[sane-devel] Net Client Not Contacting Server SOLVED

[Jörn-Ingo Weigert]

I would add, that if you want to do some scanning accounting, that you
should install saned on server even your scanner is network ready.

Accessing the scanner only through saned for the clients, stop bypassing
the server/accounting, especially when you enable authentication on the
scanner.

That the only reason where I would install saned when having a network
scanner.

Ralph Little <skelband at gmail.com> schrieb am Fr., 11. Sep. 2020, 19:54:

> Hi,
>
> On Fri, Sep 11, 2020 at 10:06 AM C. Cook <c.a.cook at quantum-sci.com> wrote:
>
>> Ok so this is to memorialize what I found with not being able to use my
>> scanner over the LAN.  Big thanks go out to Ralph Little and Olaf
>> Meeuwissen for helping with this distressing problem.
>>
>> - For local scanning you do -not- need to install/activate saned, UNLESS
>> you will be doing network scanning.  Yes, ONLY if you will be doing
>> network scanning.  But in all cases you must install sane-backends and
>> make sure that the backend in dll.conf for whatever scanner you have is
>> -not- commented out.  And install whatever client application you want
>> to use. (XSane, gscan2pdf, etc)  The client applications access the
>> backends -directly-, not through saned.
>>
>> I should point out that saned gives you networking access to scanning
> devices that do not have a native network provision.
> For scanners that natively have a networking capability, then saned is not
> required.
>
> I am glad that you managed to get some success. saned/net backend
> connectivity seems to cause a lot of unnecessary grief to many people and
> it is something that could do with better out-of-the-box support from
> distros.
>
> Cheers,
> Ralph
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20200911/71d9fe1e/attachment.html>