Problem with COM redirection

I have a XP computer that connects to a 2003-based terminal server by RDP.
We are running an application that needs a serial-communication with a terminal for credit cards (http://www.betalingsterminal.no/Betalingsterminaler-forside/Support/?tabID=0&extraTabID=1).
The application seems to start the connection, but it complaints about the data beeing transferred. I think it's because the data-stream is not as it should be. We are running 9600 baud.
Are there any way to shape the data stream for the serial communication?
stebysheAsked:
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.

johnb6767Commented:
I found this article in a similar question, not sure if it will apply though, worked for them.....

Credit Card Reader over Terminal Services
http://help.lockergnome.com/windows2/Credit-Card-Reader-Services--ftopict450183.html

Can you verify what the reader is actually transferring instead of an actual 16 digit #?
stebysheAuthor Commented:
From the application logs, it seems like the application is trying to send data to the terminal. But the application does not get any response back (acknowledgement).
This does work if we run the credit card terminal locally on the PC....but not through RDP.
PlantwizCommented:
Do you have enough licenses to run this through RDP?

C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

stebysheAuthor Commented:
Yes, we have enough TS CALs...if that is what you think of.
stebysheAuthor Commented:
The thing is that COM1, COM2, and COM3 are working in the RDP-session.... but the application for the  credit card terminal is complaining.... and it seems like this is because of the quality of the connection.  We have other equipment on COM1, and this is working just fine.
PlantwizCommented:
So you have COM1 in use for other equipment through RDP and want to add this ccard reader to COM1 also?

Have you attempted to use a different COM? or Re-assign the other devices to a different COM and let the ccard reader use COM1 if that is the default for it?


And no, I wasn't thinking TS CALs (although these are needed per connection), but does your ccard reader license permit remote use?  Or are you permitted to use it on a non-local system?  I've seen devices that require a local machine, period.  Hence my question, is this option (using RDP) even permitted with the device and licensing you have.

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
stebysheAuthor Commented:
The default for the ccard reader is COM2. We use COM2 when we run it locally.
We run other equipment on COM1. Ccard reader on COM2.
I don't know if there are any restrictions for running this reader remotely.
I have tried to get in touch with the ccard provider, but no answer today....

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
Windows Server 2003

From novice to tech pro — start learning today.