Using a serial device with terminal services.

Posted on 2006-03-31
Last Modified: 2013-11-21
We are trying to set up serial signature pads through terminal services.  I am running Windows Server 2003 as a terminal server in a Windows 2000 AD Domain.  I have Pc's running Windows 2000 with Remote Desktop Client.  RDP is set to map the serial connection on the server and the clients.  I tried net use com1: \\client\com:1, but I am still unable to get the pads to work.  The software is loaded on the server and client machines as well, and the devices will work when used locally.  Has anyone had this problem with a serial device?  Any information would be a great help!  Thanks!
Question by:aaalife
    LVL 2

    Expert Comment

    Let me see if I understand the situation:

    1.) You have Signature Pads that are hooked to your local machine.
    2.) The software (ideally) is loaded on the Win2k3 TerminalServer
    3.) The local machine (Win2k) that connects to the Win2k3 Box has these pads connected.
    4.) You want to use the signature pads hooked locally, but software is is located on the server
    5.) You have mapped the com1: locally to the TerminalServer remotely as to redirect all Com1 Traffic on the TerminalServer to the Local Machine

    Is this correct?

    How many machines simultaneously are using the TerminalServer to run this software?  Are they located across a network LAN or over the internet?

    Author Comment

    You understand the configuration correctly, it is set up on a LAN.  Right now i only have one machine that I am using for testing, but once I get it working there will be 8-10 people using them.  
    LVL 2

    Accepted Solution

    "net use com1: //tsclient/com1:" should map the proper port if each user is set to have their COM ports redirected.  Be sure to check in the user properties.  A good site to get information on for Terminal Services is:

    This guy is a MCSE and works almost exclusively with Terminal Services.  It has helped me a few times in the past when I have problems.

    Author Comment

    Turns out it was a setting in the client software causing the problem.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    What Is Threat Intelligence?

    Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

    This is an article about my experiences with remote access to my clients (so that I may serve them) and eventually to my home office system via Radmin Remote Control. I have been using remote access for over 10 years and have been improving my metho…
    Meet the world's only “Transparent Cloud™” from Superb Internet Corporation. Now, you can experience firsthand a cloud platform that consistently outperforms Amazon Web Services (AWS), IBM’s Softlayer, and Microsoft’s Azure when it comes to CPU and …
    After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
    In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor ( If you're interested in additional methods for monitoring bandwidt…

    760 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    14 Experts available now in Live!

    Get 1:1 Help Now