TWAIN+

[blackcat4866]

Here's a truly strange one.

I get a call to troubleshoot a TWAIN scanning setup to a CS-3035 (workstation XP, Server 2008). The IT guy has done everything right. It's the right TWAIN driver (1.10.1), and it's configured properly. The IP address is set correctly. It won't communicate with the scanner.

So I start from scratch. Download a fresh copy of the same TWAIN driver. Reset the NIC. Reset the IP. Unpack, load, & configure the TWAIN driver. Still won't connect.

Just to see if my scan card is functional I download, install & configure the ScanFile Utility. This works. Now the TWAIN driver is connecting & works too!?

Now I don't understand. TWAIN & FTP are entirely separate, and to my knowledge unrelated. It's just too strange. So I went to another workstation and repeated the same setup.

Again install TWAIN & configure. No connection. Install SFU & configure. It works, and TWAIN starts to work too.

Anyone care to venture an explaination? =^..^=

[Morlock49]

Maybe the problem is to do with permissions on server 2008, so when you set up SFU it was bypassing Server 2008 on the network and allowing the twain driver a different route to the copier

Only conjecture, but nice if it works.

[moderncopiertech]

First question is what scan program are you using and the second is are you putting the docs in to scan before you activate the scan program i have run into this problem before and had to remove the doc first then activaate the program.

[blackcat4866]

The app is called "eFile", and it doesn't make any difference. I experienced the same effect with Powerpoint, Publisher, Paint, really any TWAIN compatible app. Docs before connection, docs after connection, no difference.

The customer is satisfied with this solution, and I am happy when the customer is happy.