Local Printing on Remote Clients w/TS on Win2K

  • Thread starter Thread starter Mauri
  • Start date Start date
M

Mauri

How do I, or where can I find documentation on, setup
printing on each remote client when connecting to a
legacy app on win2K server using Terminal Services remote
desktop?
 
If using the latest RDP5.2 client any printer they may have installed should
be automatically mapped within their TS sessions. It will fail if the TS
does not know the drivers used.

--
Cláudio Rodrigues, MVP
Windows 2000/NT Server
Terminal Services

http://www.terminal-services.NET

-> The only Terminal Services Client for DOS.
-> The only customized RDP5.1 client with the close button disabled! :-)
-> Developers of SecureRDP, the BEST security utility for TS!

Do NOT email me directly UNLESS YOU KNOW ME or you are a Microsoft
MVP/Employee.
Use my support page on my website to submit your questions directly.
 
not sure what you mean by "It will fail if the TS does
not know the drivers used." please explain further, thnx
 
The server must be able to recognize the printer driver and must
have a driver for this printer on the TS. If the server doesn't
have the driver, the redirection will fail.
The solution in those cases is *not* to install any 3th party
printer drivers on the server (they tend to crash the spooler or
the whole server), but to map the printer to a known, native
driver. Check:

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