3224C

[stig]

hello everyone, I have a gestetner 3224c (DSc224) which is set up to print/scan via their network. The user only scans to 1 PC (XP) and uses desktopbinder. When they scan sometimes it scans ok but then when they try to scan again "NO RESPONSE FROM SCANNER 36851" is shown on the pc. Also sometimes they can preview the scanned image then when the scan button is pressed the same error code appears. I have downloaded the latest twain driver & desktopbinder version and the latest firmware is on the MFP. I also increased the memory from 256MB to 384MB. Not sure what to do next apart from swapping the print/scan controller over with another MFP that is working ok in our showroom. Thanks for any advice.

[Venom]

They twain scan so why use desktop binder?

[stig]

why not? any help or advice would be much appreciated. thanks

[Jomama46]

They twain scan so why use desktop binder?

TWAIN requires an application to pull the scan. DTB is their free app.

[Eric1968]

Why not scan to email? You don't have to install any applications.

[Venom]

You could try and set speed to 10mb instead of 100mb

[Shadow1]

...with another MFP that is working ok in our showroom. Thanks for any advice.

Time Warp! You have a 3224c in your showroom? ...and its working OK???

Look out the window and tell us what color the sky is on your planet.

We will all pray for you.

Open a command prompt and enter "ping -t <ip address>" this will do a continuous ping to the IP specified so you can see if you have any connection problems. Run a few scans and see if the connection drops or the return time jumps over a millisecond.

I've seen failing cables, hubs, NIC's, poorly configured drivers, and overloaded switches all cause similar problems.

[KenB]

The TWAIN driver uses port 1022 on the PC.

I had it happen a few (OK, more than a few ) years ago where an anti-virus utility on the PC was blocking that port, and causing the same error code you are seeing.

As I recall, it didn't happen every time; sometimes a scan would sneak through - that was the really weird part - you'd think it would always pass or always not, but noooooo.

After I allowed that port to be an exception, all was well.