Using a serial device with terminal services.

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!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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?
aaalifeAuthor Commented:
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.  
"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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
aaalifeAuthor Commented:
Turns out it was a setting in the client software causing the problem.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.