Spooler service crashes and default printer changes when clients connect via XP remote desktop

[Mike Colbert]

Windows 2000 Server DC in native AD domain with terminal services installed
in remote administration mode. Server has HP JetAdmin 3.4 software
installed. 30 printers are installed locally on the server using HP
JetDirect ports pointing to the IP address of the printer's jetdirect card.
Printers are HP LaserJets, Business InkJets, Designjets and some Savin
copier printers as well as some Minolta copier printers. Printers are
shared so clients can connect and print. 150 client PCs connect to the
print shares as their sole source of printing.

On my Windows XP PC I have a LJ 4550, Business Inkjet 2650, and Savin copier
printer installed by connecting to the shares. When I Remote Desktop to the
server, the spooler service crashes on the server and all printers become
unavailable. If I trim my printers down to just the LJ 4550 installed I
have no problems.

Are their printer compatibility issues with TS? Does anyone know of a list
showing what printers are compatible?

Additionally, when I disconnect from the server after using Remote Desktop,
the server's default printer changes to be the the last printer on the list.
Does this ring any bells?

TIA,
Mike

 

[Kris Shaw]

On my Windows XP PC I have a LJ 4550, Business Inkjet 2650, and Savin copier
printer installed by connecting to the shares. When I Remote Desktop to the
server, the spooler service crashes on the server and all printers become
unavailable. If I trim my printers down to just the LJ 4550 installed I
have no problems.

Hi,

I've had a similar problem with HP drivers on Win2k, where the spool
service crashes, mainly on the clients. It was caused by a mix of
drivers on the server which the clients were pulling down. When you
connect via TS, the drivers for your local printers are also installed
on the TS.

I would suggest that you ensure the server has as a narrow set of
drivers as possible; ie all PCL5e or PCL6 and/or Postscript. Also make
sure that the drivers are of the same revision, ie don't have a LJ4000
using driver 1.4 (made up version) and an Lj4050 on 1.5.

Kris.