In reading through the Help on the Windows Server, the
support on Microsoft's site and the Deployment Guide, I am
not finding the answers I need. In the deployment guide,
Welcome > Planning Server Deployments > Hosting
Applications with Terminal Server > Planning Network and
Hardware Resources >Planning Server Deployments > Planning
Use of Peripheral Hardware, it indicates that software
with the scanners connected to the clients should work
fine.
Here is what I am experiencing. I can connect from a
Windows 95 or 98 client machine through an RDP
connection. The software itself, runs fine. When I try
to use the scanner in the software, it works fine from one
client. As soon as the second client tries to access the
scanner, the first client is kicked out with an error and
the second client can continue fine. I have set up our
software to be using completely separate preferences,
program files and even data files from the two clients,
with the same results.
By default, the way our program uses preferences requires
that each client uses the same port for the scanner. If I
redirect the preference location so that it is unique for
each user/client, I can get two workstations to access the
scanner simultaneously, however they must be on separate
ports. If another client tries to connect on either of
the used ports, the original will be knocked out with an
error.
It is as if the server cannot allow multiple clients
access to com1 or com2 simultaneously.
If there is a setting that can be changed to allow this,
please let me know.
|
Similar Threads
Linear Mode
