Local Printer Not Availble When Using RDC

  • Thread starter Thread starter Chris W
  • Start date Start date
C

Chris W

When connecting to Server 2003, the remote client, (W2K
Professional w/SP4), does not show the local printer. The
printer does have a share, and the checkbox under "Local
Resources" has disks and printers checked. The disks work
fine, yet no printer. What am I missing?
TYIA

Chris W.
 
Probably a missing driver issue. Is there anything in the EventLog on
the TS?
 
No...Are you saying that the remote printer has to have
the driver loaded locally on the server? The only way to
do this would be install the printer on the server....how
may I do this when I cannot see the printer? TYIA

Chris W.
 
Yes, the server must be able to read the driver information from
the client, recognize the printer driver and dynamically load the
printer driver on the server. All this should be done
automatically, if there is a native driver for the printer on the
server.
If there isn't, you can either map the printer to a native driver
(the recommended approach), or install the printer on the server
and then remove the printer again, but keep the driver (not
recommended to install 3th party printer drivers, since many of
them are not full TS compatible and have a nasty habit of crashing
your spooler or the whole server).

For details, check:

294429 - Printer Redirection Architecture in Windows Server
Terminal Services
http://support.microsoft.com/?kbid=294429

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

-----Original Message-----
Yes, the server must be able to read the driver information from
the client, recognize the printer driver and dynamically load the
printer driver on the server. All this should be done
automatically, if there is a native driver for the printer on the
server.
If there isn't, you can either map the printer to a native driver
(the recommended approach), or install the printer on the server
and then remove the printer again, but keep the driver (not
recommended to install 3th party printer drivers, since many of
them are not full TS compatible and have a nasty habit of crashing
your spooler or the whole server).

For details, check:

294429 - Printer Redirection Architecture in Windows Server
Terminal Services
http://support.microsoft.com/?kbid=294429

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

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---


.
Click to expand...
 
Back
Top