Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 253
  • Last Modified:

Windows 2000 Terminal Services: Constantly Having to Restart the Print Spooler

Hey guys.

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,
Matt
0
mattx86
Asked:
mattx86
  • 2
1 Solution
 
PeteJThomasCommented:
These problems are nearly always caused by printer drivers. I would do exactly as you've suggested - Remove ALL print drivers first, then reinstall, using universal print drivers where possible...

You should hopefully find that the problem goes away after you've done that...

HTH

Pete

0
 
mattx86Author Commented:
I've asked this question three times here on EE, but this particular entry is the only one that I awarded any points on, and because of that, I want to add some more information to help others that may be experiencing this issue.

First of all, when doing this type of network printing, you must not use any driver that's labeled as one of the following:
"Host-Based"
"Plug N' Play"
"Non-Network"

If you don't see a driver on the manufacturer's website for a particular printer model that DOES NOT say any of the above three phrases, then more than likely, that printer is NOT supported under a networking environment such as Remote Desktop / Terminal Services, and is only good as a local printer for printing things directly off of YOUR computer.

If however, in the case of HP, you see a PCL or "Universal PCL" driver for your printer, then you're in luck.  Chances are very good that it will work.

The most time consuming part at this point, is distributing these same up-to-date drivers to your remote offices, and getting *ALL* of their computers using the new driver.

Of course, if your organization is large enough to have remote and/or centralized management of your remote office PC's, then it should be a piece of cake, relatively speaking.

Also, they say a Universal (PCL) Driver is best, so try it first, if your printer model supports it.  Then if that doesn't work, try that printer model's PCL driver (on both client and server).

Regards,
Matt
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.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now