Mark
asked on
Trouble connecting to HP Printer from Windows 7
I have a Windows 7 computer and an HP8710 printer. I've been printing from the Win7 to this printer for months. Today, I can't. The printer is connected to the LAN wirelessly with an IP assigned by the router. I have no wireless card in the Win7, but it's been using the LAN IP address just fine. I've run through the HP Print and Scan Doctor 5.0. I specify the Network-Wired connection. It finds the printer on the LAN saying, "The following products are visible from your computer", and it shows the 8170 and gives its IP: 192.168.0.12 and says "Installed". So, it must be able to see the printer to some extent. When I click 'Next' for it to "Communicate" with the printer, it tries for a while then says, "Failed to communicate with your selected product ..."
ALSO ... when I run the Printer Assistant, and it goes to retrieve information from the device, that succeeds! I can see the ink levels, etc.
I've shutdown/rebooted the computer several times and cycled the power on the printer (including unplugging it). I've re-done the Wireless setup Wizard on the printer. Other computers on the LAN can print w/o problem.
I can ping the 192.168.0.12 IP from 2 of the Linux computers on the LAN. I cannot ping this IP from either of the 2 Windows 7 computers on the LAN. The WIN7 *can* ping the router and other computers on the LAN.
I'm out of ideas. Perhaps a recent update to Windows did something? Perhaps a firewall issue? I need help!
(btw - I'm a network administrator at my place of employment -- and I'm stumped on this one!)
ALSO ... when I run the Printer Assistant, and it goes to retrieve information from the device, that succeeds! I can see the ink levels, etc.
I've shutdown/rebooted the computer several times and cycled the power on the printer (including unplugging it). I've re-done the Wireless setup Wizard on the printer. Other computers on the LAN can print w/o problem.
I can ping the 192.168.0.12 IP from 2 of the Linux computers on the LAN. I cannot ping this IP from either of the 2 Windows 7 computers on the LAN. The WIN7 *can* ping the router and other computers on the LAN.
I'm out of ideas. Perhaps a recent update to Windows did something? Perhaps a firewall issue? I need help!
(btw - I'm a network administrator at my place of employment -- and I'm stumped on this one!)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
John
Thanks for the update and sometimes the device goes wrong.
I would bet money that another device is using the IP address. A scan won't always product the correct result depending on how that device is configured (ie dropping incoming ICMP packets). You could try using arp to see if a result comes up for .12
i second masnrock. i strongly would recommend to using a higher number that is outside of any dynamically assigned IP numbers. if you would choose 192.168.0. 241 and higher for your static devices in order to not get the issue repeated soonly.
Sara
Sara
ASKER
(sorry for the delay. I thought I replied but must not have hit the 'Submit' button).
masnrock: I did run `arp -n`, but it found nothing for 192.168.0.12, not even for the printer! Also, keep in mind, I was able to print to this printer from Linux computer.
sarabande: My router's IP pool (dynamic) range is 192.168.0.20 - 192.168.0.126. I assign workstations, printers, etc. needing static IPs to the < 20 range. That should have the same effect as what you suggest.
Since neither Windows computer could access the printer, I have to suspect that a recent update to Windows did something, though I've not seen this on other sites I'm responsible for. Who knows! Changing the IP to .11 seems to have fixed the problem.
masnrock: I did run `arp -n`, but it found nothing for 192.168.0.12, not even for the printer! Also, keep in mind, I was able to print to this printer from Linux computer.
sarabande: My router's IP pool (dynamic) range is 192.168.0.20 - 192.168.0.126. I assign workstations, printers, etc. needing static IPs to the < 20 range. That should have the same effect as what you suggest.
Since neither Windows computer could access the printer, I have to suspect that a recent update to Windows did something, though I've not seen this on other sites I'm responsible for. Who knows! Changing the IP to .11 seems to have fixed the problem.
ASKER
I fixed it