Link to home
Start Free TrialLog in
Avatar of furuno
furuno

asked on

Cannot ping or print from one Win 10 workstation

7 PCs in an office here all running Windows 10

Network = workgroup

New router installed with IP address of 192.168.1.254

Canon photocopier / printer with IP address of 192.168.1.50

All PCs can print perfectly  bar 1 PC which cannot. When initially set up - worked great for 1 week.

When you ping printer (ping 192.168.1.50)  it responds " response from 192.168.1.254 destination unreachable"

What could the problem be?
Avatar of Joshua Hopkins
Joshua Hopkins
Flag of United States of America image

Check the cable/wifi connection.  What is the ip address of that machine?  Can it ping the gateway 192.168.1.254?
Avatar of furuno
furuno

ASKER

yes it can ping the gateway 192.168.1.254
Are all the ip address static or DHCP?  Can it ping other computers on the network?
Avatar of furuno

ASKER

All are DHCP. It can ping other computers on network.
ASKER CERTIFIED SOLUTION
Avatar of John
John
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of furuno

ASKER

ok thanks guys I will try these solutions when on-site again and will report back
Avatar of furuno

ASKER

solved!

The reason it could ping is because the printer had changed IP address.

when users were asked if the printer was working. They all reported "yes". They were infact using a 2nd printer - a printer they were not meant to be using!

Two lessons here. Printers must be statically assigned in the router and the IT admin should never ever trust end-user reports. Observe them instead and always test the problem for yourself (even if it does mean asking a user to relinquish their seat for 15mins in a busy work environment).  

Printer's IP address was statically assigned and port number changed in client devices. All works perfect now.

Thanks for the great advice dispenced  by all the JH's!
Author acknowledged that our solutions helped here.