Home › Forums › TWAIN Classic › Twain on a Terminal Server
- This topic has 1 reply, 2 voices, and was last updated 11 years, 5 months ago by MarkM.
- AuthorPosts
We have a weird issue with the TWAIN Data source in Terminal Server.
Application detects the TWAIN DS fine, it loads the DS successfully however it does not recognize the local scanners.
Our Application is written inI am using C# and the .NET framework 3.5
The drivers are installed under user’s profile and we load the libarary from the user’s profile
the same code works fine on Desktop.
Somehow the redirection of twain does not work. Any help is appreciated. Thanks.The TWAIN Data Source Manager looks for .ds files inside of the TWAIN_32 directory. If those data sources respond to a DG_CONTROL / DAT_IDENTITY / MSG_GET, then they are listed. That does not mean that the physical scanner is connected or ready for use. The application doesn’t find that out until the DG_CONTROL / DAT_IDENTITY / MSG_OPENDS command is issued.
So that explains why you’re seeing the “device”…you’re really seeing the driver, not the device…
When you run “Remote Desktop Connection” click the Options arrow (bottom left corner) to see the advanced settings. Go to the Local Resources tab and press the “More..” button at the bottom of the dialog.
Confirm that “Ports” is checked, and that “Other supported Plug and Play (PnP) devices” is checked, then check “Devices that I plug in later”.
There’s no guarantee that USB redirection works for the scanner you’re using, but if it does, that’ll set it up. If that doesn’t work, then you’ll need to hunt around for a redirector option for Terminal Server, or investigate other options like Silex (using the net to access a USB device), or something like Citrix, which has a TWAIN redircetor…
- AuthorPosts