The first place to look for the problem is in the TS Event Log, as it will
have a logged event when the printer is not auto-created, that will explain
why.
Do NOT modify the NTPrint.inf file. This doesn't work anymore, as of 2000
SP2. You must create a user defined inf file and edit the registry to point
to this file. You can find a sample on this page:
http://www.workthin.com/tsp.htm
or you can download a wizard driven application from Microsoft that will
create this file & registry entry:
http://download.microsoft.com/download/9/f/2/9f237742-e057-4e00-a0d5-62de2ebf9fbd/TSPDRW_Package.exe
Post by PatriotI have already tried installing the 4200 drivers on the server. I will try
modifying the NTPrint.inf file. Thank you.
Post by Patrick RouseDrivers are NOT built-in for the LaserJet 4200, but this model will work fine
with the 4050 driver. If the printers are attached to the client machines,
either locally or via TCPIP port, you'll need to map the LaserJet 4200 to the
4050 driver via user defined inf file, or install the 4200 driver on the
server (the user defined inf file is safer).
http://www.workthin.com/tsp.htm
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
Post by PatriotMy client workstations are running both Windows 2000 Pro and XP Pro with all
the updates applied.
We just purchased several new HP LaserJet 4200's. When they connect using
remote desktop, their new printers do not show up. The older printers show up
but not the HP LJ 4200's. How do I correct this? Thank you.