Check the EventLog on the Terminal Server to see why the printer is
not redirected.
Basically, there are 2 areas where printer redirection can fail:

1. redirection is not attempted at all (no Events att all in the
EventLog)
Solution: check the configuration of local device redirection in
the RDP client, update the client to the latest version, which
supports redirection of network printers and apply KB article
302361 in case of a non-standard local port name

302361 - Printers That Use Ports That Do Not Begin With COM, LPT,
or USB Are Not Redirected in a Remote Desktop or Terminal Services
Session
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 3th 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.

If you are running Windows 2003 SP1 on your Terminal Server, you
can configure a Fallback printer driver.

According to
HP Printers Supported in Citrix MetaFrame Presentation and Terminal
Server Environments
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?
objectID=c00213455

the HP LaserJet 3200 is suported in a TS environment.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Boe" <boe_d@notspam.hotmail.com> wrote on 18 dec 2005 in
microsoft.public.windowsnt.terminalserver.setup: