Re: Terminal server remote printing

My guess is that both of your problems have the same cause:
the servers which don't autocreate your local printers don't have
the appropriate drivers for those printers.
Verify this by checking the EventLog on the server.

From the "Printing" menu in http://ts.veranoest.net/

Basically, there are 2 areas where printer redirection can fail:

1. redirection is not attempted at all
Solution: check the configuration of printer redirection in the RDP
client and on the Terminal Server, update the RDP client to at
least the XP SP2 version or apply KB article 302361 to get support
for redirection of non-standard local port names, including tcp/ip
ports.
http://support.microsoft.com/?kbid=302361

2. redirection is attempted, but fails because the server doesn't
have a driver for the printer
Solution: whatever you do, do not install a 3rd party printer
driver on the Terminal Server, unless it is a Windows Hardware
Quality Labs (WHQL) signed driver. Many non-WHQL drivers are not
TS-compatible, and some are known to crash your printer spooler or
the whole server. In stead, map the printer to a native driver by
creating a custom ntprintsubs.inf file, as described in KB article
239088.
http://support.microsoft.com/?kbid=239088
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?Sm9lIE1jSGFl?= <JoeMcHae@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 15 jan 2007 in
microsoft.public.windows.terminal_services:

I have a windows 2003 domain with two windows 2000 terminal
servers running Citrix presentation server 4.0. Printing has
been a problems since before I came onboard. My question today
is 2fold
(1) When I remote desktop to any of my 2003 servers I
do not see any of my local printers being recreated on the
servers.
(2) of the 2 windows 2000 terminal servers only one is
autocreating any printers for the Citrix users. I recently
re-loaded both of those servers so they would be identical,
evidently not. I have checked the RDP and ICA connection
properties on all the servers they are all configured to
autocreate locaal printers. One last thing the local printers on
my workstation are network printers, but on other networks this
has never been a problem.
.

Relevant Pages

  • Re: Enterprise NLB Terminal Server Print Spooler Jam. New Flavor
    ... is connecting by a cable modem, and one is connected by a ... clustered terminal servers as IP printers with local ports. ... print jobs moving again is to 1. ...
    (microsoft.public.windows.terminal_services)
  • Enterprise Print Spooler Jam. New Flavor
    ... The problem I am writing about has to do with print spoolers that seem ... to keep getting jammed up for no reason. ... clustered terminal servers as IP printers with local ports. ...
    (microsoft.public.windows.server.general)
  • Enterprise NLB Terminal Server Print Spooler Jam. New Flavor
    ... The problem I am writing about has to do with print spoolers that seem ... to keep getting jammed up for no reason. ... clustered terminal servers as IP printers with local ports. ...
    (microsoft.public.windows.terminal_services)
  • Re: HP 2420 Printers
    ... > We have several 2000 servers in our network. ... > printers from HP 2300 to HP 2420. ... Unable to add driver. ... Event log errors? ...
    (microsoft.public.win2000.general)
  • Re: print management
    ... "Robert Britton" wrote: ... >>> We have several HP JetDirect based print servers as well ... >>> networked printers with built in network adapters. ... I need the ability to have a night manager move jobs between printers ...
    (microsoft.public.win2000.printing)