Printer ready but not printing -- Server 2003

I can ping printer and enter its internal web page.  It prints local config pages.  The other 50 printers on the server are having no problems.

Restarting the print spooler does nothing.

What other tasks could I do besides rebooting the server?

LVL 9
Sean MeyerAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Alan_WhiteConnect With a Mentor Commented:
The idea of printing from a client directly was just to narrow down the fault.  If that had worked, it would have pointed to the server and a reboot would have been the next option.

As for why, go figure!  Sometimes Windows just likes a reboot.  That said, I have a 2003 box with over 800 queues hanging off it and while the spooler needs a kick every now and again, it rarely needs a reboot.

Is there anything of not in the system log?  Services stopped etc.
0
 
Alan_WhiteCommented:
Double check all the settings on the print server for the port settings.
Try turning off Advanced Printing features and bi-direction

Set up the printer on a client PC (or another server) with TCP/IP printing, see if it's the printer or the server.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
How is it connected? USB? Network?  Are you sure the connections are working properly?
0
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

 
devinnoelCommented:
Restarting the spooler service should take care of ALMOST all Printer issues that rebooting would.

Have you cycled power on the printer itself?
Try making sure there isn't an IP conflict (ping -t printername, unplug the printer, ping should start failing), although if you can get to the config webpage that's probably not it.
Can you setup a print queue on your workstation to print to the printer directly rather than to the queue on the server?
0
 
Sean MeyerAuthor Commented:
Ok I had power cycled the printer... No Ip confict.  I did not try to print directly to the printer instead of the queue but I am guessing that would have worked but that is not a solution as the printer is the default printer for certain documents for 200 computers.  Those documents auto-print without user interaction.

I did reboot the server and 28 documents in queue printed lickity split.  Ok what might have been the issue and how could I have corrected the issue without the reboot?

Thanks!
0
 
devinnoelConnect With a Mentor Commented:
Adding a queue to your local workstation is a troubleshooting step, not a solution. If you can print locally, but not from the server that isolates things to a problem on the server & not the printer.

Bouncing the print spooler service fixes 95% of print queue problems that aren't printer problems... Unfortunately you appear to be in that remaining 5%.

What type of printer is it?

Does it have the latest drivers? If not I'd try updating them. Switching from PCL drivers to PostScript or the other way around may help as well. I prefer PostScript to PCL drivers in general, I find them less problematic & more reliable.
0
 
Sean MeyerAuthor Commented:
Yes there are error messages.  I have been getting them over the last while since my server started receiving the documents which auto-print.

Faulting application spoolsv.exe, version 5.2.3790.4759, faulting module ntdll.dll, version 5.2.3790.4789, fault address 0x0002c6e4
Faulting application spoolsv.exe, version 5.2.3790.4759, faulting module ntdll.dll, version 5.2.3790.4789, fault address 0x0002a1fd.
Faulting application spoolsv.exe, version 5.2.3790.4759, faulting module ntdll.dll, version 5.2.3790.4789, fault address 0x0002ade1

Everything usually prints fine and may need a spooler restart.  I get these errors about once a month on average with the need to reboot. I only reboot servers as needed for windows updates.  Do you recommend rebooting on a weekly schedule?
0
 
Sean MeyerAuthor Commented:
Printer type is a Dell 5210 (Lexmark core)
0
 
devinnoelConnect With a Mentor Commented:
Historically I've always found my print server to be my least stable server, probably due to all the various drivers installed for all the various printers. A weekly reboot at midnight or something rarely hurts, especially on a print server.

Definitely look at updating your print drivers. Those are by far the most likely cause of the spooler errors & the ensuing printing problems.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.