D
Don
I have only one printer which has been giving me fits ever since we upgraded
to server 2003. We have over 20 printers on our network and this one HP5si
will display a dialog on the print server saying the following:
The printer was unable to connect to your printer. This can be caused by
your printer being turned of, the cable being unplugged, or being connected
to a VPN, which will block your access to your local network.
Here is what I have tried:
Replaced the jetdirect card after it fried (it was doing this prior to the
card going).
Removed the printer from the server and created a new printer (along with
drivers).
Checked the firmware on the printer, it is the latest
Replaced the network patch cord
Put the patch cord into another port
It does not error contantly, it will error a few times a day, and not to one
particular user. We have three 5si printers and this is the only one giving
me the problem, as a matter of fact this is the only printer giving me a
problem. We recently upgraded from NT 4.0 to 2003 with active directory. So
I strongly suspect this is an active directory issue.
Any suggestions?
Thanks
to server 2003. We have over 20 printers on our network and this one HP5si
will display a dialog on the print server saying the following:
The printer was unable to connect to your printer. This can be caused by
your printer being turned of, the cable being unplugged, or being connected
to a VPN, which will block your access to your local network.
Here is what I have tried:
Replaced the jetdirect card after it fried (it was doing this prior to the
card going).
Removed the printer from the server and created a new printer (along with
drivers).
Checked the firmware on the printer, it is the latest
Replaced the network patch cord
Put the patch cord into another port
It does not error contantly, it will error a few times a day, and not to one
particular user. We have three 5si printers and this is the only one giving
me the problem, as a matter of fact this is the only printer giving me a
problem. We recently upgraded from NT 4.0 to 2003 with active directory. So
I strongly suspect this is an active directory issue.
Any suggestions?
Thanks