<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
Hi,<br>
<br>
<div class="moz-cite-prefix">On 2021-05-08 2:13 p.m., Media Mouth
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:361527B5-4E20-4F7D-B3F0-5EBB0BE0A2CE@gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On May 8, 2021, at 1:27 PM, Ralph Little <<a
href="mailto:skelband@gmail.com" class=""
moz-do-not-send="true">skelband@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><span style="caret-color: rgb(0, 0, 0);
font-family: Avenir-Book; font-size: 14px; font-style:
normal; font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none; float: none; display: inline
!important;" class="">Do you have 192.168.0.15 in
/etc/sane.d/saned.conf?</span></div>
</blockquote>
</div>
<div class=""><br class="">
</div>
<div class="">Yes.</div>
<br class="">
<div class="">Though I wonder if I misunderstood what `saned.conf`
is doing.</div>
<div class="">I thought for remote scanning it's in play server
side, as opposed to client side.</div>
<div class="">the LAN IP of the Client Machine would need to be
what's listed in the <span style="font-family: Avenir-Book;"
class="">/etc/sane.d/saned.conf file on the Server machine.</span></div>
<div class=""><br class="">
</div>
</blockquote>
Yes, no point changing the saned.conf on the client side.<br>
On the server, add 192.168.0.15 to saned.conf on a line on its own.<br>
<br>
<blockquote type="cite"
cite="mid:361527B5-4E20-4F7D-B3F0-5EBB0BE0A2CE@gmail.com">
<div class="">In any event I've tested with Client IP in the
Server Machine's <span style="font-family: Avenir-Book;"
class="">/etc/sane.d/saned.conf</span></div>
<div class=""><span style="font-family: Avenir-Book;" class="">and
the Server IP in the Client Machine's </span><span
style="font-family: Avenir-Book;" class="">/etc/sane.d/saned.conf</span></div>
<div class=""><span style="font-family: Avenir-Book;" class=""><br
class="">
</span></div>
<div class=""><font class="" face="Avenir-Book">No luck yet either
way.</font></div>
</blockquote>
It's always frustrating trying to figure out when saned/net is not
working.<br>
We should look at the server side since it looks like the client is
doing the right things.<br>
<br>
Firstly, are you sure that the server side is seeing 192.168.0.15 as
the incoming address? If you are accessing it through PAT or NAT
(like often from a VM), then saned is going to see your external
address rather than your internal address.<br>
Just thought I would bob that in there, not to insult your
intelligence. ;)<br>
<br>
Secondly, we can try to switch on debugging. When saned is running
as a service it should be outputting diag to the syslog.<br>
We should be able to increase the level of that by editing the init
line.<br>
On my system (which is Linux Mint 19.3) saned is kicked off by the
init process and is listed in /etc/inetd.conf:<br>
<br>
sane-port stream tcp nowait saned:saned
/usr/sbin/saned saned<br>
<br>
Add -d10 to the end of the line and that should increase the
verbosity of the output to the syslog.<br>
<br>
sane-port stream tcp nowait saned:saned
/usr/sbin/saned saned -d10<br>
<br>
Try to connect again, then check the bottom of the syslog.<br>
<br>
Cheers,<br>
Ralph<br>
<br>
</body>
</html>