| Next: How to determine if a client is Local or Remote |
| Author |
Message |
Wingman External

Since: Apr 04, 2006 Posts: 2
|
Posted: Tue Apr 04, 2006 4:49 pm Post subject: Credit Card Reader over Terminal Services Archived from groups: microsoft>public>windowsnt>terminalserver>misc (more info?) |
|
|
I have a remote location that is using Terminal Services to access Billing
Software. We are now starting to accept credit cards and have bought a card
swipe from EMS. At the main location where the Billing Software is run
through the local network, the swipe reader works fine. However over TS the
reader, which emulates a keyboard will not work properly. At the beginning
of the card number there is supposed to be a % sign. When swiping on the
local machine the percent sign is there, but when swiping in a TS session,
the first character is a 5.
I can use PC Anywhere to log into the Terminal Server and swipe properly as
well. Unfortunately, PC Anywhere will not serve our purpose as there are 4
users at the remote location that need access at the same time.
I also tried holding the shift key while swiping, which did work to change
the 5 into a %, but it also messed up the remainder of the numbers. Checked
with cap locks on and off.
Tech support for the card swipe are baffled, tech support for the billing
software also puzzled, and a couple of local MCSE techs are unsure of a
solution.
Any ideas would be greatly appreciated. |
|
| Back to top |
|
 |
Wingman External

Since: Apr 04, 2006 Posts: 2
|
Posted: Tue Apr 04, 2006 5:10 pm Post subject: Re: Credit Card Reader over Terminal Services [Login to view extended thread Info.] Archived from groups: per prev. post (more info?) |
|
|
|
| BTW, the reader is connected to the local machine via USB
|
|
|
| Back to top |
|
 |
jenniferb

Joined: Nov 06, 2006 Posts: 1
|
Posted: Mon Nov 06, 2006 5:38 am Post subject: Re: Credit Card Reader over Terminal Services [Login to view extended thread Info.] |
|
|
| I am experiencing the same problem, has anyone come up with a solution yet? |
|
| Back to top |
|
 |
VMagius

Joined: Jul 02, 2007 Posts: 2
|
Posted: Mon Jul 02, 2007 10:11 am Post subject: [Login to view extended thread Info.] |
|
|
| This is wild, but there's a work around if you are doing it the same way I am. Don't use the terminal in full screen. I was finally able to get it going with terminal services in a window. Not the best option, but whatever works until a real solution comes up. |
|
| Back to top |
|
 |
VMagius

Joined: Jul 02, 2007 Posts: 2
|
Posted: Tue Jul 10, 2007 10:53 am Post subject: [Login to view extended thread Info.] |
|
|
Talked it over with a card manufacturer. The trouble seems to be in your client side terminal program. There is a setting in there that needs to be changed.
For Windows Remote Desktop, hit the option button -> Local Resources Tab.
Change the Keyboard option to "In Full Screen only". It might be one of the other options. Just play with it. |
|
| Back to top |
|
 |
jman2800

Joined: Apr 08, 2009 Posts: 1
|
Posted: Wed Apr 08, 2009 12:04 pm Post subject: [Login to view extended thread Info.] |
|
|
Taken from
http://blogs.parivedasolutions.com/jtownes/archive/2007/05/14/418.aspx
Resolution
The resolution is fairly simply yet obscure.
When you connect to the terminal server (or remote desktop session), click Options, navigate to the Local Resources tab, and set the “Apply Windows key combinations” setting to “On the local computer” instead of the default “In full screen mode only”. Thanks to Nathan Caneday for finding this one |
|
| Back to top |
|
 |
|