[sane-devel] Net Client Not Contacting Server

Ralph Little skelband at gmail.com
Wed Sep 9 15:31:36 BST 2020


On 2020-09-06 8:11 a.m., C. Cook wrote:
> On 2020-09-05 22:57, Olaf Meeuwissen wrote:
>>>> In dll.d there is iscan which contains:
>>>> epkowa
>>>> net
>> This is on the server, right?  Because its the server that communicates
>> with the device via the epkowa backend.
> This is on the server.  So maybe I don't even need net on the server.
That's correct, you don't need the net backend on the server side.
I feel that the net/saned setup is not well documented in general and
many people have problems setting this up.
In fairness, a lot of the problems that people experience are related to
the vagaries of networking, often to do with firewalls and such like.

The net backend is for the client and it talks to to saned. Saned runs
on the server and talks to your non-networked hardware, and acts as your

First things first, we should make sure that the net client is trying to
dial out to saned, as you state that you cannot see port 6566 traffic there.

As Olaf suggests., could you try

SANE_DEBUG_NET=128 scanimage -L

...on the client and capture the output and post it here?

At least we should be able to see what the net backend is up to.


More information about the sane-devel mailing list