TS2003 Network Twain Driver, in the Terminal Services forum on BrianMadden.com

I have been trying to get this network twain driver to work for a canon copier (Canon Network Scangear software) on my test terminal server. When terminal services is not installed it works perfect, but if I install TS then the apps cannot find the scanner driver. Any help would be greatly appreciated.
Thanks

Try installing the twain driver after TS is installed. There is a warning that states that applications may not function correctly if they were installed before terminal services. As well, it may be that the driver is not compatible with terminal services. You should contact the vendor to find out if it's supported.

I have tried both ways.

But I did finally get it to work. It looks like the twain_32.dll that comes with windows does not function in terminal services mode(at least not in 2003). First of all to get anywhere you need to copy twain_32.dll, twain.dll, twunk.exe, twunk_32.exe and the twain_32 directory from the windows folder to your home folder(docs and settings\username\windows\). That got rid of some of the errors I was getting but it still didn't work, so I looked at another terminal server that was using remote scan twain driver and I noticed the twain_32.dll on that server was different and was created by the remote scan install. So I copied remote scan's twain_32.dll from that server to my test server and now the scanner shows up and scans. Anyone know why the standard twain_32.dll from Microsoft doesn't work with terminal services?

I am currently having the exact same issues, but I don't have remote scan available to me. I am using the same software and have installed it only after first setting the terminal server into application mode. Here's what really makes it interesting. When using IrfanView to acquire a scanner image, it won't work at all when the TS is set for /execute mode. But when I change to /install mode, it works perfect. Something happens when changing this setting that makes it stop working. Any clues here? I can make this thing work, but it's not a solution of course. Any ideas would help a great deal.

Any reason you are not using RemoteScan?

We are currently in the process of migrating our remaining 2000 terminal servers to 2003. In 2000, scanning worked like a champ and we had no need for a 3rd party solution--The Canon Color Network ScanGear solution "just worked". I am only beginning to learn that 2003 terminal server scanning is nothing at all like it was in 2000. I guess you could say it's a hard pill to swallow thinking that scanning took steps backwards in 2003 and I'm going to have to consider a 3rd party solution in 2003 to do what I did in 2000. I only discovered this last week and am making certain that this is what I have to do before I push ahead further.

Problem solved!!

See article CTX107411 on Citrix WEB or Q186499 on Microsoft.

Locate the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\Myapp

Where Myapp is name of EXE for scanning application. For example MSPSCAN for Office Document Scanning.

Click Add Value, and create DWORD with name Flags .
Set value to 0x408

From Q186499:
If the "Do not substitute user Windows directory" bit is set, it retains the SystemRoot directory for GetWindowsDirectory API calls. If this bit is not set, all paths to the Windows directory are replaced with the path to the user's Windows directory.

And Network ScanGear works in Office Document Scanning now.

MI.T

Thank you so much for figuring this out. I have a TS 2003 and I am having the same problems as you. I took your advice and went into the registry but unfortunately my software that I need to work is not located under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\SCANSOFT

Do I have to manually place "myapp" as you did with MSPSCAN ?

Any help would be greatly appreciated