Navigation
Sticky FAQs
- Reactivate/Transfer a license
- TS Easy Print
- How can I become a Thinstuff Reseller?
- Installation and usage of TSX Scan
- I have a problem but I cannot find the ...
- XP/VS Server versions
- Installation and Usage of TSX RemoteApp
- Uninstall XP/VS Server
- Single session per user
- Auto Printer Creation
- TSX Session Broker
- Activate XP/VS licence
- TSX RemoteApp
- XP/VS Server trial version
- Invalid hardware key?
Records in this category
- Allow logon through Terminal Services XP and SBS03
- Auto Printer Creation
- Auto Reconnect
- Calculate RAM usage
- Change RDP Listen Port
- Client drive mapping
- Connect with RDP Client
- Enable 24-bit color depth
- Enhanced Application Compatibility
- Keep-alive packets for RDP sessions
- Kiosk Mode
- Login with blank password
- RDP client download links
- RDP LPT port mapping
- RDP serial port mapping
- RDP Session Timeout
- Reconnect from any client W2k3
- Redirect keyboard input to server
- Reduce bandwidth
- Remote Control
- Shutdown menu Windows 7
- Single session per user
- Smart card redirection
- Start remote applications with RDP client
- TS Easy Print
- TSX USB
- How can I add users to the Remote-Desktop-User group in Windows XP?
- Hardware requirements
- I have a problem but I cannot find the answer in the FAQ site?
- TSX RemoteApp
- Update XP/VS Server
- Terminalserver compatibility of third party applications
- Microsoft Office with XP/VS Server
- XP/VS Server detected as Trojan on Windows XP
- 32Bit vs. 64Bit operating systems with XP/VS Server
- TSX Session Broker
- XP/VS Server manual
- XP/VS Server trial version
- Aero Glass Remoting
- Audio Capture
- Media Player Redirection
- Detect XP/VS version resource programatically
- Is the XP/VS Server compatible with Windows Server 2000?
- Support for Network Level Authentication on Windows XP SP3
- How can I add users to the Remote-Desktop-User group in Windows Home OS?
- Allow domain user logon to XP/VS Server
- Font smoothing for RDP Sessions to XP SP3
- Install XP/VS Server on Server operating systems
- Uninstall XP/VS Server
- How can I share an USB Device with TSX USB?
- Demo license
- Font Sizes / DPI-Scaling in Remote Desktop Sessions
- TS RemoteApp vs. TSX RemoteApp
- TSX Connection Manager
- Prevent remote users from shutting down/rebooting the XP/VS Terminal Server
- XP/VS with Operating System-Level Virtualization
- XP/VS Server & True Multimonitor Support
- How can XP/VS Terminal Server limit a specific user to a single application at RDP login
- Copy & Paste via Clipboard Redirection in RDP Sessions
- How can I sign my .rdp files?
- XP/VS Server and ThinClients
Tags
XP/VS Server » Technical
RDP serial port mapping
First make sure that you've enabled port redirection in the Remote Desktop Connection client:
- In the Remote Desktop Connection window, click Options.
- On the Local Resources tab, under Local devices, make sure that "Ports" is checked !
- Click Connect and now inside your RDP connection all your local serial ports will be available via the same port name (COM1, COM2, ...).
Example:
Let's assume your client-workstation has two built-in serial ports COM1, COM2 and you've also attached an USB-to-SERIAL converter which shows up as COM5 in the device manager.
Now if you launch a remote desktop session from that workstation to the Thinstuff XP/VS Terminal Server any communication within the remote desktop session with COM1, COM2 and COM5 will be redirected to your client-workstation's local (physical) COM1, COM2 and COM5 port.
In other words: Inside the remote desktop session you will get "virtual serial ports" that have the same name as your client-workstation's physical ports.
Important note:
If you have to communicate with the server's own physical serial port from within a remote desktop session you should change the numbers of the server's physical com ports to a higher value in the server's device manager (e.g. from com1 to com11 and com2 to com12).
In this way if you open com1 from within a rdp session your client-workstation's com1 will be opened and if you open com11 within the same rdp session the server's com1 will be accessed instead.
Known limitation for connections TO Windows XP:
If your XP/VS Terminal Server is running on Windows XP then only one user can open a redirected port with the same name at a time. Example: If User1 and User2 are connected to Windows XP and both users have redirected their ports then User2 won't be able to open his redirected COM1 while User1 is accessing his COM1 in the other rdp session. As soon as User1 closes the application which is using COM1, User2 will be able to open his port again. For small installations a simple workaround is to change the client's com port numbers in order to avoid conflicts. (This limitation only applies to rdp sessions TO Windows XP.)
Tags: local resources, map com in rdp, redirect hardware, serial port mapping
Last update: 2011-03-15 14:55
Revision: 1.11