Thanks. We also have the keyboard wedge scanners on our parts counters and they work fine but the handheld one docks with a docking station and uses a serial. I will look at those registry settings.
Main Topics
Browse All TopicsI have been banging my head on a wall with this one so any help is appreciated.
I have a Percon PT 2000 bar code scanner. We have software that does dispatching and inventory that is designed to use only this specific scanner. This scanner has its own memory, it is designed to scan a number of items and then it docks to a PC--it connects via a serial cable--you click an import button in the software, and it imports the Part # and Quantity into the software. This all works fine in our home office which does not use citrix.
I have also gotten this to work via an RDP session, I did have to be sure the "Connect Automatically...." to the Serial devices was checked in the RDP Options of the client.
In Citrix the first item and it's quantity get sent over. Then I just get a transmit error--but it should be noted that this error is in what almost looks like a hyperterminal box that the scanner uses. I get no errors in citrix or the inventory software. The scanner has some test software that you can use called PTFER which just sends the scanned items over to a text file. I get the same results there, RDP works fine, Citrix, first line comes through (i.e. xxxxxxxx, 12) and then the transmit error.
I set up the com redirection in Citrix and TS, and I have run net use com1: \\client\com1: from a command prompt. If I type in net use it shows the com is mapped correctly. I have also examined CTX384590 http://support.citrix.com/
I have already tried troubleshooting this with the makers of the scanner (PT2000) and they say it is set up correctly from what they can tell.
I have Citrix PS 4.5 Enterprise on Win 2K3 servers.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The settings I posted are just the defaults to show you where it the registry they are. This kind of thing can be tough, but it you got it working through Terminal Server, you should be able to make it work through Citrix. You want to make sure there is no software running locally that would grab control of the serial port. In other words if there are any drivers or little helper apps for that scanner, they should not be running on the client when using Citrix. They may need to run on the server and the server controls the serial port through the mapping.
One more thing to check is if you have any settings that would prevent serial port mapping (Such as Citrix policies or configuation on the ICA listener). It sounds like it worked briefly so that is not likely a problem.
I believe the policies are good, I have no citrix policies in place other than farm settings. I have a test server with no applications other than our database, I will do some testing today to see what else is running and let you know. I am thinking it may be some sort of two-way communication that is not going through. It sends the first line, and then maybe the scanner is waiting for a response to send the next line?
It is a serial bar code scanner. You can use it with a keyboard wedge also, but I cannot get it to work that way either. It can connect either with a cable connected directly to the scanner or through a docking station. A manual for it is here: http://www.posguys.com/dow
Not sure what you mean by the distance for the remote terminal and desktop, it is not a wireless scanner. The information is stored in the PT 2000, when you dock it you click an import button from our software and send data from the scanner and it moves it over. This works fine in a normal setup and in a remote desktop session. Yet when I try it in citrix with the same server that it works on in a RDP it only sends the first item over.
This question is getting old and I haven't been able to find the solution so I am going to give the points to amccrea as those pointers at least gave me more info to go on. I have decided to go ahead and just let the five users that will need this scanner use Terminal Server and bypass citrix as I could not find another way.
thanks for the ideas.
Business Accounts
Answer for Membership
by: a-mccreaPosted on 2008-04-02 at 15:43:42ID: 21268284
I don't know specifics on your scanner (The ones I use just show up as a USB keyboard), but hope this piece of info helps as I had some headaches trying to tweak serial until I learned this...
RE\Citrix\ ICA Client\Engine\Configuratio n\Advanced \Modules\C lientComm] " N.DLL" W.DLL"
In the new Citrix client versions (10 and newer), the serial polling settings have been moved from wfclient.ini to the registry.
Here is where they are
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWA
"AllowForeignIRQShare"="No
"COM1IRQ"="4"
"COM1IOP"="0x3f8"
"COM2IRQ"="3"
"COM2IOP"="0x2f8"
"COM3IOP"="0x3e8"
"COM3IRQ"="4"
"COM4IOP"="0x2e8"
"COM4IRQ"="3"
"CommPollWaitIncTime"="20"
"CommPollWaitInc"="1"
"CommPollWaitMax"="500"
"CommPollWaitMin"="0"
"CommPollSize"="On"
"DriverNameWin32"="VDCOM30
"DriverNameWin16"="VDCOM30
"DriverName"="VDCOM30.DDL"
"WindowSize"="1024"