using Scanners with Windows Terminal Services

  • Thread starter Thread starter Tim Sheehan
  • Start date Start date
T

Tim Sheehan

I am trying to connect scanners to people's workstations who are using
Windows Terminal Services, and I have hit a brick wall.

How the $#@#@$ can they access their own local scanners????

Anyone else have this problem??

Help!
 
Local scanners are NOT supported natively with Terminal Services or any 3rd party enhancement package like Citrix MetaFrame, Canaveral iQ, HOB, Panther..., whether connected via LPT, USB or SCS

I've heard of network based scanners (connected via Ethernet, similar to a JetDirect Card) that may work, but have no intimate knowledge of these, so I can't confirm or deny its' validity

http://groups.google.com/[email protected]&rnum=1

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Tim Sheehan wrote: ----

I am trying to connect scanners to people's workstations who are using
Windows Terminal Services, and I have hit a brick wall

How the $#@#@$ can they access their own local scanners???

Anyone else have this problem?

Help
 
There's a reply on microsoft.public.windows.terminal_services about a product that might help you. http://www.remote-scan.co

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co



----- Patrick Rouse [MVP] wrote: ----

Local scanners are NOT supported natively with Terminal Services or any 3rd party enhancement package like Citrix MetaFrame, Canaveral iQ, HOB, Panther..., whether connected via LPT, USB or SCS

I've heard of network based scanners (connected via Ethernet, similar to a JetDirect Card) that may work, but have no intimate knowledge of these, so I can't confirm or deny its' validity

http://groups.google.com/[email protected]&rnum=1

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Tim Sheehan wrote: ----

I am trying to connect scanners to people's workstations who are using
Windows Terminal Services, and I have hit a brick wall

How the $#@#@$ can they access their own local scanners???

Anyone else have this problem?

Help
 
Tim,

can you please crosspost next time (i.e. post a single message to
multiple newsgroups), in stead of posting separate posts to all
terminal server newsgroups? I've replied to a number of your post
in the other newsgroups, will repeat myself once more here.
If you want to continue this thread, please set a follow-up-to
newsgroup, to avoid having multiple separate discussions in
multiple newsgroups.

Now for the content :-)

We use a product called ScanShare Pro from Netcore. It is network
device with a network connection and a SCSI port (much like a
network printer server device, but with a SCSI port in stead of a
parallel port). You can then access the scanner via the network.
It is fully supported in a TS / Citrix environment and works
perfectly in our test environment.

http://www.netcore.com.tw/product.htm

RemoteScan from http://www.remote-scan.com/
lets you share any kind of TWAIN scanner (SCSI / USB / Firewire,
etc.)

LWP DokScan for RDP
http://www.lwp.de/distribution/distr_produkte_details.jsp?id=161
(web site in German)

Some scanner models (e.g. HP Scanjet 7400, connected to a
workstation via USB) include network scanner sharing, and are
accessible by terminal server users.
 
The RemoteScan software from http://www.remote-scan.com works for us.

It as long as the scanner is twain compatible, it works with all scanners.
Works with terminal services too, and just solved a crisis for us. Quite happy!
 
Back
Top