Hi Dave,
I've spent some time trying to get network scanning going with saned and I'm so close I can smell it... but not quite there. 'Scanimage -L' works fine remotely, but when I try to do 'scanimage > scan.pnm', I hear the scanner initialize, then there is a 30 second lull, then the scanner initializes again and an error show on the remote machine: 'scanimage: sane_read: Error during device I/O'. I'm pretty sure I got all the proper settings in the various conf and TCPIP files.
Is there a way to set up debugging of the network interface of SANE?
I haven't tried saned ina number of years. I did a quick google and found
http://penguin-breeder.org/sane/saned/It suggests:
You can start saned with debugging enabled. To do this, you to disable the saned in your inetd.conf or xinetd.conf - otherwise you will get an error message telling you that saned couldn't bind a port. Just comment it out with hash-marks (#) or stop the whole inetd or xinetd server. Then start saned from the command line like this
# SANE_DEBUG_MUSTEK=128 saned -d128
(assuming you have a Mustek SCSI scanner, see the man page of your backend for the exact name of the debug variable). If you are using csh or tcsh, you need to use setenv to set the debug variable.
Maybe you can find the error from the output yourself, if not, you can include it into a mail to the sane-devel mailing list. There should also be some output in your syslog.
On the client side you should use something like
$ SANE_DEBUG_NET=128 scanimage -L