[sane-devel] No scanners detected on LTSP fat client when net.conf uses hostname

[John Hupp]

I remember you from the Alt Linux and/or ALTSP lists.  It's a small world.

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.

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:
_server_ _fat client_ _standalone_
$ host <ltsp-servername>             127.0.1.1 127.0.1.1              
<ltspserverIP>
$ /etc/resolv.conf                           127.0.0.1 
<ltspserverIP>     127.0.0.1

So indeed, the fat client and standalone are handling those 
differently.  I'll look into it further.   Thanks!

On 5/7/2015 2:54 AM, Michael Shigorin wrote:
> On Wed, May 06, 2015 at 03:14:37PM -0400, John Hupp wrote:
>> 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.
> Fix resolving on your LAN / within the served image, this has
> nothing to do with SANE (I've been doing ALTSP, trust me :) --
> http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html#ss5.5 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.
>
>> 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.
> 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.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20150507/a3964650/attachment.html>