Windows 2000 Terminal Services: Constantly Having to Restart the Print Spooler
Posted on 2009-04-08
For the last 3-4 months, we've had to restart the Print Spooler on our Windows 2000 Server, anywhere from 2-5 times a day! Our remote offices will call in saying it won't print to their local printer, and a few seconds after restarting the Print Spooler, you will hear the page print out over the phone.
We've tried scheduling a batch file to restart the Print Spooler every so often, but it doesn't appear to be helping.
Today, a co-worker came up with an idea that's crossed my mind before, but never has it been so tempting to try: Gather a list of all remote printers used and their latest Win2k drivers, and then remove all printer drivers from the server and reinstall them all. (I'm sure there's atleast 2 or 3 printer drivers no longer in use, as printers were swapped out over the years.)
This is driving me batty!
Thanks in advance,