<html>
<head>
<meta content="text/html; charset=koi8-r" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I remember you from the Alt Linux
and/or ALTSP lists. It's a small world.<br>
<br>
I noted in the original post that a fat client can ping the server
hostname successfully, and also that a standalone on the network
with a net.conf configured with the server hostname successfully
scans with the scanner server.<br>
<br>
I thought those were very solid indicators that this is not a name
resolution issue, but I do get some indicators of that very issue
from host and resolv.conf output:<br>
<u>server</u>
<u>fat client</u> <u>standalone</u><br>
$ host <ltsp-servername> 127.0.1.1
127.0.1.1 <ltspserverIP><br>
$ /etc/resolv.conf 127.0.0.1
<ltspserverIP> 127.0.0.1<br>
<br>
So indeed, the fat client and standalone are handling those
differently. I'll look into it further. Thanks!<br>
<br>
On 5/7/2015 2:54 AM, Michael Shigorin wrote:<br>
</div>
<blockquote cite="mid:20150507065459.GT19034@imap.altlinux.org"
type="cite">
<pre wrap="">On Wed, May 06, 2015 at 03:14:37PM -0400, John Hupp wrote:
</pre>
<blockquote type="cite">
<pre wrap="">The last step is configuring /etc/sane.d/net.conf for sane
clients, identifying saned hosts either by hostname or IP
address. I find that using the hostname works on another
actual standalone machine on the LAN, but it fails with the fat
clients. So far I can only make fat client scanning work by
entering an IP address.
</pre>
</blockquote>
<pre wrap="">
Fix resolving on your LAN / within the served image, this has
nothing to do with SANE (I've been doing ALTSP, trust me :) --
<a class="moz-txt-link-freetext" href="http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html#ss5.5">http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html#ss5.5</a> might help.
Start with "resolve" or "host" commands on the fat client
and cite your /etc/resolv.conf when asking for help on
e.g. #ltsp at irc.freenode.net.
</pre>
<blockquote type="cite">
<pre wrap="">But the server gets its IP address by DHCP, a feature I want to
preserve so that I don't have to get into the router
configuration when I set one of these up.
</pre>
</blockquote>
<pre wrap="">
If you don't run a farm of servers, you generally want their
LAN IPs configured statically and not dynamically (and if there
was a real reason to do DHCP for *servers* you would know better
already); if your router leases 192.168.1.2+ and has some range
like "2-200" for the last octet, you can put the server at .254
and be done with that.
</pre>
</blockquote>
<br>
</body>
</html>