Terminal Server client printing

  • Thread starter Thread starter Nic
  • Start date Start date
N

Nic

Hi Everyone,

I have a workgroup of machines. 1 being the TS. All
the clients are in different areas and we can't figure out
how to get control of the printers. It looks like they
are printing, but I don't know where they are going. The
printers are attached to the clients themselves and I
thought that when a user logs in the drivers are supposed
to be uploaded?

What am I missing? I have HP printers and don't know
where they are all coming from?

Nic
 
I'm not quite sure what you mean by "I don't know where they are
going" and "where they are all coming from", but I assume that
autocreation of the users local printers doesn't work (at least
not always, and not for every printer), and print jobs are maybe
appearing on the wrong printer?

It is true that the Terminal Server loads the driver
automatically, provided that it *recognizes* the locally attached
printer. And that's often where the problem lies. If the local
printer driver name does not match *exactly* with the printer
driver name on the TS, then the TS does not recognize the printer
and doesn't autocreate it.
If you try to fix this by manually assigning a printer to a TSxxx
port, then printouts in subsequent sessions can end up all over
the place, since TSxxx ports are re-assigned dynamically.

If this describes your problem, you will have to create a custom
ntprintsubs.inf file to map the local printer driver name to a
native driver on the server.

Details are explained here:

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

317780 - Print Jobs That Are Sent to Terminal Services Redirected
Printers May Print on Another Client's Printer
http://support.microsoft.com/?kbid=317780
 
umm. In simple terms. Printer Drivers will not upload from a client to the
Terminal Servser.

The Printer Driver name on the client must match one in the Terminal Servers
list of printers.

2 ways around..
1. Load the printer driver from disk (or file) on the Terminal Server
connecting to a File: port then delete the printer. The drivers will remain.
2. Do a whole bunch of .inf file modifications to hack in the unsupported
printer driver.

Option 2 is the recommended way for some reason.
Option 1 works perfectly well most of the time.

:)
 
I wouldn't say that option 1 (installing a 3th party printer
driver on the Terminal Server) works "perfectly well most of the
time"!
The reports in these newsgroup about crashing spoolers and
crashings servers caused by TS-incompatible printer drivers are
numerous.
If you want a stable environment, do *not* install 3th party
printer drivers, but use native drivers.
 
Amen to that!

And simply follow the suggestion that Vera made with the ntprintsub.inf file
( along with the two registry entries ).

HTH,

Cary
 
Back
Top