SEO

Hmmm I sure hope some can help me before all my hair is
pulled out!!

After many unsuccessful attempts and much reading of docs on
saned I am now completely insaned myself !!!!

Half the time I cant follow the instructions properly
because either files do not exist saned.users as one
example, hosts.allow as another saned not in expected
directory and much more

These are the steps I have taken so far to get saned up and
running

configured saned.conf in /etc/sane.d/saned.conf with several
ip addresses allowed to access saned.

net.conf also in /etc/sane.d/net.conf

configured epson.conf my scanner I know this works, because
I can scan from server using xsane

added /etc/hosts.allow and put ip addresses of machines in
it

checked that sane 6566/tcp #saned network scanner
daemon
exists in /etc/services and it does

set up xinetd.conf as per sane page for network scanning

set up dll.conf and made sure net was not # out it isnt

when not successful with saned from xinetd.conf

tried as recommended using debug mode
/usr/sbin/saned -d
and got the horrible message below, why is it not allowing
this machine to connect, after all it is in the saned.conf
and net.conf files and now hosts.allow.

why does it insist that address already in use?
how can I find which address is using 6566 ??

I have used kde systemguard to try and find what is using
6556 but it does not list this as a used port

After initial bind failed error I can see the saned in kde
systemguard it dies when I try and connect from a machine
that should be allowed according to saned.conf and net.conf

please can anyone tell me what is occuring here

TIA
Yeric

[saned] main: starting debug mode (level 2)
[saned] main: [1] bind failed: Address already in use
[saned] saned (AF-indep+IPv6) from sane-backends 1.0.12
ready
[saned] check_host: access by remote host:
::ffff:10.10.10.10
[saned] check_host: getaddrinfo failed: Name or service not
known
[saned] init: access by host ::ffff:10.10.10.10 denied
[saned] quit: exiting

[1]+ Done /usr/sbin/saned -d

On Sat, 30 Aug 2003 10:06:17 +0100
Yeric <eric.heaton2@btinternet.com> wrote:

> set up xinetd.conf as per sane page for network scanning
What did you set up xinetd.conf for?
Should xinetd listen on port 6566 and spawn a saned process?
If so you have to configure that in saned so that it is aware of the
fact that it doesn't listen on the port itself.
You typically change the mode from standalone to inetd

> tried as recommended using debug mode
> /usr/sbin/saned -d
> and got the horrible message below, why is it not allowing
> this machine to connect, after all it is in the saned.conf
> and net.conf files and now hosts.allow.

> why does it insist that address already in use?
> how can I find which address is using 6566 ??

> [saned] main: starting debug mode (level 2)
> [saned] main: [1] bind failed: Address already in use
If xinetd is configured this way it is listening on this port already,
thus causing saned to fail.

But you should be able to find xinetd listening on that port with
netstat -pl

Hope that helps

Daniel Willmann

Daniel Willmann wrote:

> On Sat, 30 Aug 2003 10:06:17 +0100
> Yeric <eric.heaton2@btinternet.com> wrote:
>
>> set up xinetd.conf as per sane page for network scanning
> What did you set up xinetd.conf for?
> Should xinetd listen on port 6566 and spawn a saned
> process? If so you have to configure that in saned so that
> it is aware of the fact that it doesn't listen on the port
> itself. You typically change the mode from standalone to
> inetd

Hi Daniel, I have now disabled xinetd and removed with
rc-update delete xinetd


> But you should be able to find xinetd listening on that
> port with netstat -pl
>
Hmmm even with xinetd service stopped and removed nothing
shows in netstat for 6566 and still get the same error

so inetd is better than xinetd ???

I cant understand this, these machines can connect to
internet, cups, samba without problems just not saned

> Hope that helps

A little thanks

>
> Daniel Willmann