Hi, On 2021-05-08 3:23 p.m., Media Mouth wrote: > Haven't yet tried the "-d10" debugging > But even before doing that, checking over syslog. The following are > the most suspicious lines: > > "inetd[444]: sane-port/tcp: bind: Address already in use" > > "saned[2038]: read_config: could not open config file > (saned.conf): No such file or directory" >
Yeah, that seems pretty suspicious. :D > "saned[2038]: init: access by host ::ffff:192.168.1.182 denied" > > That seems to imply you have an incoming connection from that address (192.168.1.182) which is weird, but might be unimportant. Let's try to simplify the situation a little. We can try to run saned manually, no need to stop the service, we can choose a different port. saned -l -p 7000 -b 192.168.0.Server -e -d10 This will run saned binding to the port 7000 in the foreground, channeling the diag to stderr instead of syslog. Perhaps list the output of that in a reply here. You won't be able to connect a client to it without editing the client's /etc/services file to change sane-port to 7000 from 6566 which is a bit of a faff. There is no way to configure the client's net backend to choose a non-standard port. It merely looks at the machine's services configuration. :( Please check that you do not have SANE_CONFIG_DIR set in your environment, unless it is set to /etc/sane.d. That optionally contains the directories to search for the config file. If it still cannot find saned.conf, and you do not have the var set, you could set it to /etc/sane.d and try again. ----- Setting up saned/net can be a frustrating process. Usually it either "just works" or doesn't for frustratingly opaque reasons. :D Cheers, Ralph
