it sees the printer but cant print

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a XP PRO wired to a Belkin Router. I have a HP OfficeJet V40 connected
via USB to the XP machine. They print fine. I even have another XP wired to
the router and via the network it prints fine. The trouble is when I connect
my laptop to the network. I can share files great. I can even see the printer
on the network. I add it to the laptop (vista, and have tried Mac OSX) which
is connected via the WIRELESS on the router. It wont print! It HAS worked
before in this setup. I restored the router to default settings. No change.

any ideas would help
THANKS!
 
Gena said:
I have a XP PRO wired to a Belkin Router. I have a HP OfficeJet V40
connected
via USB to the XP machine. They print fine. I even have another XP wired
to
the router and via the network it prints fine. The trouble is when I
connect
my laptop to the network. I can share files great. I can even see the
printer
on the network. I add it to the laptop (vista, and have tried Mac OSX)
which
is connected via the WIRELESS on the router. It wont print! It HAS worked
before in this setup. I restored the router to default settings. No
change.

any ideas would help
THANKS!

I assume when you say the laptop can see the printer you can 'ping' the
printer from the laptop. If my assumption is correct it would appear to
point to a laptop printer driver problem. I suggest you delete then
reinstall the printer driver.
 
Gena said:
I have a XP PRO wired to a Belkin Router. I have a HP OfficeJet V40
connected
via USB to the XP machine. They print fine. I even have another XP wired
to
the router and via the network it prints fine. The trouble is when I
connect
my laptop to the network. I can share files great. I can even see the
printer
on the network. I add it to the laptop (vista, and have tried Mac OSX)
which
is connected via the WIRELESS on the router. It wont print! It HAS worked
before in this setup. I restored the router to default settings. No
change.

Whenever I encounter this sort of problem 9 times out of 10, it's a firewall
blocking the access.
 
Back
Top