Terminal Server local lpt port corruption

By craig ·
I have a Windows 2003 Server users connect to remotely via RDC. This server has a local printer on LPT1, an Okidata ML320. Some users connecting remotely also have this same printer model connected directly to their PCs. Recently the LPT1 port on the server has become corrupted to the point I have to remove and reinstall the port several times a day. This started happening when one particular user started using RDC with the same Okidata ML320 printer attached to their PC. Could this connection be causing the corruption or is something else possibly causing it?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Terminal server tries to map local printers in the server

by stephanvaningen In reply to Terminal Server local lpt ...

Possibly, TS is configured to map the printers and other local settings in the remote session.
You can disable this setting on client level (Options of RDC) or on server level:
Go to Administrative Tools, Terminal Services Confguration: right-click on a connection and choose properties: the tab 'Logon settings' let's you disable the possibility of clients to mess-up server services (i.e: if you sign in with a client using a printer with a driver not known by the server, the server's print spooler service crashes!)


Related Discussions

Related Forums