Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a client(Windows 7 Pro) that make a connection to Windows terminal server through RDP, i have enabled COM port redirection for both server and client side, but the redirection doesn't happen ...

The client don't have a native mainboard COM port, but have an USB-TO-Serial adapter (Prolific USB-to-Serial), it is possible redirect this USB-TO-Serial COm Port ?

share|improve this question
up vote 1 down vote accepted

If you're running 2008r2 and win 7 ultimate, you do have the option to look at remotefx USB redirection... to redirect USB devices... or look at 3rd party software like this.

share|improve this answer

It's not currently possible without 3rd party software. Windows sees this device as a USB device, not a COM port (yes I understand the irony). RDP doesn't currently support remote USB devices (hopefully some day it will).

share|improve this answer

I don't think the accepted answer here is entirely correct.

Right next to me is a barcode scanner connected to a Prolific USB2Serial adapter connected to a Windows 7 client (with installed Prolific Drivers). The Client sees this Prolific Adapter as COM3.

Now if I connect to any terminal server while allowing ports to be mapped (Options > Local Resources > More. Check "Ports"), that virtual COM3 will be available on the Terminal Server with no problem.

So to answer the question:

If you can install drivers on the Terminal Server Client machine and you install the Prolific driver, then you can enable Port redirection on the Client and the Port will be available and working correctly on the Server.

If you can't install drivers on the client, you will need an external 3rd party software as it was linked by @TheCompWiz

share|improve this answer
Unfortunately again, the terminal server NEVER sees the "COM3". It seems strange I know, and appreciate... but I believe there is code in the MSTSC to deliberately ignore any & all serial ports associated with a USB adapter. This is true for usb-serial adapters, as well as devices that have serial interfaces (gps receivers & such) I'm currently battling this problem with an embedded gps receiver. – TheCompWiz Nov 19 '10 at 1:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.