<div>I only have the one eth interface being used on the server, but since I have the cable plugged into the third port, it comes up as eth2 instead of eth0.</div><div><br></div>Ok, so here is the client's relevant ifconfig info:<div>
<div><div>wlan0 Link encap:Ethernet HWaddr 00:19:7e:57:45:35 </div><div> inet addr:192.168.17.52 Bcast:192.168.17.255 Mask:255.255.255.0</div><div> inet6 addr: fe80::219:7eff:fe57:4535/64 Scope:Link</div>
<div> UP BROADCAST MULTICAST MTU:1500 Metric:1</div><div> RX packets:31284 errors:0 dropped:0 overruns:0 frame:0</div><div> TX packets:31597 errors:0 dropped:0 overruns:0 carrier:0</div><div>
collisions:0 txqueuelen:1000 </div>
<div> RX bytes:18173897 (18.1 MB) TX bytes:9295105 (9.2 MB)</div></div><div><br></div></div><div><br></div><div>Here is /etc/sane.d/net.conf from the server:</div><div><div># This is the net backend config file.</div>
<div><br></div><div>## net backend options</div><div># Timeout for the initial connection to saned. This will prevent the backend</div><div># from blocking for several minutes trying to connect to an unresponsive</div><div>
# saned host (network outage, host down, ...). Value in seconds.</div><div>connect_timeout = 60</div><div><br></div><div>## saned hosts</div><div># Each line names a host to attach to.</div><div># If you list "localhost" then your backends can be accessed either</div>
<div># directly or through the net backend. Going through the net backend</div><div># may be necessary to access devices that need special privileges.</div><div>localhost</div><div>127.0.0.1</div></div><div><br></div><div>
<br></div><div><br></div><div>And here is /etc/sane.d/saned.conf from the server:</div><div><div># saned.conf</div><div># Configuration for the saned daemon</div><div><br></div><div>## Daemon options</div><div># Port range for the data connection. Choose a range inside [1024 - 65535].</div>
<div># Avoid specifying too large a range, for performance reasons.</div><div>#</div><div># ONLY use this if your saned server is sitting behind a firewall. If your</div><div># firewall is a Linux machine, we strongly recommend using the</div>
<div># Netfilter nf_conntrack_sane connection tracking module instead.</div><div>#</div><div>data_portrange = 10000 - 10100</div><div><br></div><div><br></div><div>## Access list</div><div>localhost</div><div>127.0.0.1</div>
<div><a href="http://192.168.17.1/24">192.168.17.1/24</a></div><div># A list of host names, IP addresses or IP subnets (CIDR notation) that</div><div># are permitted to use local SANE devices. IPv6 addresses must be enclosed</div>
<div># in brackets, and should always be specified in their compressed form.</div><div>#</div><div># The hostname matching is not case-sensitive.</div><div><br></div><div>#scan-client.somedomain.firm</div><div>#192.168.0.1</div>
<div>#<a href="http://192.168.0.1/29">192.168.0.1/29</a></div><div>#[2001:7a8:185e::42:12]</div><div>#[2001:7a8:185e::42:12]/64</div><div><br></div><div># NOTE: /etc/inetd.conf (or /etc/xinetd.conf) and</div><div># /etc/services must also be properly configured to start</div>
<div># the saned daemon as documented in saned(8), services(4)</div><div># and inetd.conf(4) (or xinetd.conf(5)).</div></div><div><br></div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Nov 25, 2012 at 6:31 PM, Olaf Meeuwissen <span dir="ltr"><<a href="mailto:olaf.meeuwissen@avasys.jp" target="_blank">olaf.meeuwissen@avasys.jp</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Please reply to the list so that others can chime in and find a solution<br>
to your problem (if any).<br>
<div class="im"><br>
Joel Webster writes:<br>
<br>
> Relevant output of "sudo ifconifg":<br>
> eth2 Link encap:Ethernet HWaddr 00:e0:4c:f8:68:6c<br>
> inet addr:192.168.17.19 Bcast:192.168.17.255 Mask:255.255.255.0<br>
> inet6 addr: fe80::2e0:4cff:fef8:686c/64 Scope:Link<br>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
> RX packets:1220938 errors:0 dropped:0 overruns:0 frame:0<br>
> TX packets:758956 errors:0 dropped:0 overruns:0 carrier:0<br>
> collisions:0 txqueuelen:1000<br>
> RX bytes:1027283786 (1.0 GB) TX bytes:1079186151 (1.0 GB)<br>
> Interrupt:23 Base address:0xa000<br>
<br>
</div>Hmm, "eth2" ... looks like you have more than one network interface.<br>
<br>
Is this on the server or the client? Ideally, I'd like to see both.<br>
<div class="im"><br>
> Output of "grep setfacl /lib/udev/rules.d/*-libsane.rules":<br>
> ENV{libsane_matched}=="yes", RUN+="/bin/setfacl -m g:scanner:rw<br>
> $env{DEVNAME}"<br>
><br>
> Output of "groups saned":<br>
> saned : saned<br>
><br>
> Output of "sudo service saned status":<br>
> saned is running.<br>
><br>
><br>
> I can see that I have a discrepancy in the "groups saned" output. I have<br>
> added the saned user to the scanner group and I have verified that "groups<br>
> saned" returns both saned and scanner. I have restarted the saned service,<br>
> but I still cannot scan via the network, not even through localhost on the<br>
> server.<br>
<br>
</div>Which leaves us waiting for your configuration files.<br>
<div class="im HOEnZb"><br>
>> For lack of a crystal ball ;-), posting your /etc/sane.d/net.conf and<br>
>> /etc/sane.d/saned.conf files as well as information about your network<br>
>> configuration would be very helpful in trouble shooting this.<br>
<br>
</div><div class="HOEnZb"><div class="h5">Hope this helps,<br>
--<br>
Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION<br>
FSF Associate Member #1962 Help support software freedom<br>
<a href="http://www.fsf.org/jf?referrer=1962" target="_blank">http://www.fsf.org/jf?referrer=1962</a><br>
</div></div></blockquote></div><br></div>