Re: Net scanning

Raymond A. Ingles (inglesra@frc.com)
Fri, 10 Sep 1999 09:20:30 -0400 (EDT)

On Thu, 9 Sep 1999, Petter Reinholdtsen wrote:

> > Now, it just fails. So it appears that I'm contacting frakir.
>
> What do you get if you do 'telnet frakir 6566'?

Zip. No output; if I try to type anything, the connection closes.

> Tru to run scanimage with SANE_DEBUG_NET=128 to get more debug info.

Okay, when I run the command on "grayswandir" (the computer trying to
scan from across the network), I get:

---------------------------------
$ SANE_DEBUG_NET=128 scanimage -d net:frakir:mustek:/dev/scanner -l 0 -t 0 -x 10 -y 10 >scan.pnm
[sanei_init_debug]: Setting debug level of net to 128.
[net] init: could not find `saned' service (Success); using default port 6566
[net] open("frakir:mustek:/dev/scanner")
[net] adding backend frakir
[net] connect_dev: network protocol version mismatch: got 2, expected 1
scanimage: open of device net:frakir:mustek:/dev/scanner failed
[net] exiting
[net] closing dev 0x804cdb8, ctl=-1
---------------------------------

Now, here's the really interesting part. When I run the *identical*
command on frakir (the computer with the scanner physically attached), I
get...

---------------------------------
$ SANE_DEBUG_NET=128 scanimage -d net:frakir:mustek:/dev/scanner -l 0 -t 0 -x 10 -y 10 >scan.pnm
[sanei_init_debug]: Setting debug level of net to 128.
[net] adding backend localhost
[net] adding backend grayswandir
[net] open("frakir:mustek:/dev/scanner")
[net] adding backend frakir
[net] read: next record length=48 bytes
[net] read: next record length=-1 bytes
[net] exiting
[net] closing dev 0x804dca0, ctl=4
[net] closing dev 0x804e190, ctl=-1
[net] closing dev 0x804e128, ctl=-1
---------------------------------

Okay, so... hmmm. I've checked; the binaries are identical for
"scanimage" and "saned" on both machines. I'm running Debian 2.1, and the
version of SANE is a little outdated:

Version: 0.74-2

So, anyway, what could cause it to work on the local host and not
remotely? Do I need to muck with the "saned.conf" and "net.conf" files on
grayswandir? I must be doing something stupid somewhere...

> Try my earlier syslog patch,

Haven't had a chance to try that yet, sorry.

Sincerely,

Ray Ingles (248) 377-7735 ray.ingles@fanucrobotics.com

"COBOL is here for the long run... [O]n the Starship Enterprise make
no mistake, the program that calculates their pay will be written
in COBOL..." - Jerome Jahnke

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com