unable to print to ANY laser printers

[cameramonkey]

We have a handful of users spread across our enterprise that suddenly cannot print to ANY of our HP Laserjets of various models anywhere in our WAN.

Whether they attempt to print a test print to the print server's IP directly or printing through the print queue on the server, they receive the "failed to print" error. They can print to our MFC devices, inkjets, etc without problem. Others in the network print just fine.

I have tried updating drivers, uninstalling/reinstalling drivers, etc. But that doesnt seem to help.

Ideas?

 

[linney]

Does this experience give you any clues?

Cannot print to certain printers on my office network.

http://forum.soft32.com/windows/ers-office-network-ftopict359650.html

Anecdotally I have heard that allowing HP to do Automatic software updates often tends to break things after a round of updates, I wonder if there is a grain of truth in that?

Are there any errors showing in any of the relevant Event Viewer logs?

Stopping of the Print Spooler
thread779-686557

You could also try your luck in some of the Server Forums.

http://www.tek-tips.com/threadminder.cfm?pid=931

 

[cdogg]

Regarding the users having problems, can anyone else print successfully to the laserjets they're trying to print to? I'm trying to determine whether it's a handful of PC issues or if it's on the printer side.

Were there any recent network upgrades or changes? Were there recent Microsoft patches pushed across the network to each workstation?

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Einstein
[tab][navy]For posting policies, click [/navy]here.

 

[cameramonkey]

As I said, (although not 100% clearly) the printers appear to be fine otherwise. Other users can print to the "failed" printers just fine.

Its just a handful of users (5 out of 400) that suddenly cant print to those types of printers.

 

[linney]

Can the users who cannot print to the Laserjets, print to them if they logon at a different machine of a user who can print? Conversely can the users who can print still print if they log on to a non-printing user's machine?

As a test have you tried removing one of the users and their machine from the Domain and rejoining them?

Has HP any ideas on the matter?

 

[cdogg]

Following in line with Linney's suggestion, I would also test to see if another user (who has never logged into that PC before) has the same issue on the problem PC. The goal here is to see if a corrupt Windows profile has anything to do with the issue.

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Einstein
[tab][navy]For posting policies, click [/navy]here.

 

[cameramonkey]

Sorry it took so long. it took a while to get my hands on the PC.

It appears that its not a profile issue. After logging in using a fresh profile, it still gives me the same error.


One thing I noticed, is that the test print error is absolutely instantaneous. The PC doesnt hesitate a bit. before my finger can come back up off the mouse button, its displaying the "failed to print" error.

 

[kmills]

In the HP printer itself (try accessing it through the web page) you can sometimes set Server IPs. Have those computers that can't print been blocked at that level?

Or, if using a print server, have those users been excluded under Security settings?

 

[cameramonkey]

there is nothing between here and the main printer in question but routers and a private MPLS cloud. We do not use any security interally that would prevent the communication. The test user I just attempted to use is a domain/enterprise admin.... there is nothing that account CANT do.

originally the PC was on the same LAN segment as the printers with nothing but switches between it and the printers. Now its across the MPLS. And thats what makes me think its a local issue. there wasnt any time for the network to respond, even if it WERE local. Now that its across the WAN there should at least be a momentary delay before erroring out.


I'm also pretty sure its not a network issue, as the workstation is able to access the jetdirect device web pages.


We have replaced the user's computer with a new one, and now its running fine. It MUST be something on this old workstation that is causing the problem.

 

[BadBigBen]

Just a thought, when the PC was moved, did you uninstall the printer and then reinstalled it? or was the network info the only change that was done...

what I am thinking is that the printer's original network path was still in affect and through the move in the network, it did not find it...





Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[cameramonkey]

Ben: I'm afraid I'm not following you. the network path for the printer has not changed.

I can move ANY sytem around my enterprise network and printers never have to be changed. I simply moved the PC (which uses DHCP) from one location to another because I am at HQ and this problem PC was at a satellite location.
the move is a non issue. The problem existed when it was on the user's desk.

 

[BadBigBen]

originally the PC was on the same LAN segment as the printers with nothing but switches between it and the printers. Now its across the MPLS.

That is a major change...

and that is why I asked if the printer was removed and then reinstalled...


Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."