How to connect Hp Officejet 5255 Printer to Computer or phone?

HP Officejet 5255 Printer Connection error & troubleshooting:

1. Power off the HP Officejet 5255 printer, network router, and computer.
2. Restart the devices one by one. Wait until the router gets a stable network connection.
3. Power up the printer and establish the connection.
4. Examine the line connectivity from the computer.
5. Assign a static IP to the printer, if the issue is unresolved.
6. Utilize the EWS page of the printer to assign a static IP and manual DNS address.
7. Ensure that you are entering the appropriate address and Ip on the page.
8. Close the page and restart the printer.

Computer and phone cannot connect error reset:

1. Remove all the connections from the wireless router and power it off.
2. Remove the power cord from the printer and the computer to turn them off.
3. Restart the router after 60 seconds and wait till the connection is stable.
4. Power up the printer and connect the router. Wait for the printer to get connected with the router.
5. Switch on the computer and check if the issue is resolved. If it persists, continue to the next step of assigning a static IP and manual DNS to the printer.
6. In the control panel touch the wireless icon, and look for the IP address of the printer. Type the address in the web browser of your computer and open the EWS page of the printer.
7. Click on the Network tab and choose the Wireless (802.11) option. Click on the Network address (IPv4) option to open the tab for assigning the static address.
8. Choose the radio button next to the Manual IP bar and choose the Suggest a manual IP address option from the page. Now enter the static IP Address to be assigned to the computer. Click on the OK button.
9. Now choose the Radio button that displays Manual DNS Server. Type 8.8.8.8 in the manual preferred type box. Enter 8.8.4.4 in the manual alternate type box. Save the settings and close the EWS page of the device.
Connect the device to a computer and try reconnecting again. The issue should have got resolved with the complete network reset.