[sane-devel] Cannot connect to saned
Henning Meier-Geinitz
henning at meier-geinitz.de
Mon Dec 29 16:45:25 GMT 2003
Hi,
On Mon, Dec 29, 2003 at 05:26:37PM +0100, Hauke Coltzau wrote:
> I'm trying to configure saned to access my HP PSC 2110 from
> both clients in my network. I'm using YaST on S.u.S.E. 9.0
> to configure the client. When typing in the IP address of my
> sane server (192.168.0.1), YaST tells my that no scanner was
> found on this host.
Better try without Yast. This way you know what you are doing :-)
> On the other hand, the sane server itself seems to be fine,
> since I can run scanimage -L on localhost and telnet to
> port 6566 from both localhost and remote.
So it doesn't look like a saned problem on first sight. What happens
when you do:
scanimage -d net:192.168.0.1 -T
That should do a test scan on the first scanner of the server.
If that works, just put "192.168.0.1" in net.conf of the client.
> If I run saned in debug level 128, I can find following
> lines telling me that saned grants access to my client but
> then simply exits:
>
> [saned] check_host: access granted from IP address ::ffff:192.168.0.2 (IPv4-mapped)
> [saned] init: access granted
> [saned] init: access granted to saned-user@::ffff:192.168.0.2
> [saned] process_request: waiting for request
> [saned] process_request: got request 1
That's "sane_get_devices"
> [saned] process_request: waiting for request
> [saned] process_request: got request 10
That's "sane_exit".
> [saned] quit: exiting
saned did exactly what you told him to do (probably "scanimage -L"?) :-)
In debug mode, saned exits after each connection.
Does scanning work? I.e. id you start saned in debug mode on the
server, does "scanimage -d net:192.168.0.1 >image.pnm" on the client
scan something? If not, what's the error message?
Has saned on the server the necessary permissions to access the scanner?
Bye,
Henning
More information about the sane-devel
mailing list