> On May 8, 2021, at 3:59 PM, Ralph Little <[email protected]> wrote: > > That seems to imply you have an incoming connection from that address > (192.168.1.182) which is weird, but might be unimportant. I've been bouncing between different systems each with a client/client/scanner (so maybe best to just express them as ClientIP and ServerIP) The above LAN is a client IP.
> 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 From this I get: saned: invalid option -- 'l' So wasn't able to test via port change. > 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. This was not set (i.e. no evidence of it from `printenv`, but based on your note I added the following line to /etc/environment on the server: SANE_CONFIG_DIR="/etc/sane.d" LMK if I did that correctly. Wasn't sure if /etc/environment is the right file, or whether to put /etc/sane.d vs /etc/sane.d/ (i.e. with or without trailing slash) Tested both but still getting the same results from SANE_DEBUG_NET=10 scanimage -L
