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? =^..^=
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? =^..^=
Comment