Saned port shows good but not connecting over network
by mark9117 from LinuxQuestions.org on (#4WN7N)
Greetings. If this question is not in the appropriate location, please move it. Thanks.
I recently upgraded my file server to a current Mageia version. In doing so, I have lost some things despite restoring good backups. One of the things I'm missing is my network scanner. The scanner (details below) is connected to the server via USB and has been working just fine for years. It still works on the server locally, but I can no longer get my Mageia 7 desktop to connect to it. Again, it all worked just fine prior to the upgrade. I see this as network trouble rather than an issue with saned specifically. I may be wrong.
Here are some details.
Linux shuttle 5.4.2-desktop-1.mga7 #1 SMP Thu Dec 5 17:40:00 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
(from "scanimage -L" on the server) device `genesys:libusb:002:002' is a Canon LiDE 110 flatbed scanner
scanimage (sane-backends) 1.0.27; backend version 1.0.28
Scanner works locally on server (192.168.1.105), but does not work from a desktop on the LAN (192.168.1.106). I am unable to connect to port 6566 on the server via telnet. Connection closes immediately:
# telnet shuttle 6566
Trying 192.168.1.105...
Connected to shuttle.
Escape character is '^]'.
Connection closed by foreign host.
scanimage -L on the desktop fails to see the scanner
saned is running:
# systemctl status saned.socket
a- saned.socket - saned incoming socket
Loaded: loaded (/etc/systemd/system/saned.socket; enabled; vendor preset: disabled)
Active: active (listening) since Sun 2019-12-15 20:41:33 MST; 13h ago
Listen: [::]:6566 (Stream)
Accepted: 36; Connected: 0;
Memory: 128.0K
CGroup: /system.slice/saned.socket
Dec 15 20:41:33 shuttle systemd[1]: Listening on saned incoming socket.
saned.socket shows open and listening per other tools as well:
nmap -sV shuttle -p 6566
Starting Nmap 7.70 ( https://nmap.org ) at 2019-12-16 10:34 MST
Nmap scan report for shuttle (192.168.1.105)
Host is up (0.00015s latency).
PORT STATE SERVICE VERSION
6566/tcp open tcpwrapped
# netstat -l |grep sane-port
tcp6 0 0 [::]:sane-port [::]:*
my user is in the server's "scanner" group
saned is in "lp" group
Firewalls are down
/etc/saned/net.conf
## saned hosts
::1
localhost
192.168.1.106
192.168.1.105
/etc/hosts.allow is set for ALL:ALL
Does anybody have any ideas?
Thanks.
Mark
I recently upgraded my file server to a current Mageia version. In doing so, I have lost some things despite restoring good backups. One of the things I'm missing is my network scanner. The scanner (details below) is connected to the server via USB and has been working just fine for years. It still works on the server locally, but I can no longer get my Mageia 7 desktop to connect to it. Again, it all worked just fine prior to the upgrade. I see this as network trouble rather than an issue with saned specifically. I may be wrong.
Here are some details.
Linux shuttle 5.4.2-desktop-1.mga7 #1 SMP Thu Dec 5 17:40:00 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
(from "scanimage -L" on the server) device `genesys:libusb:002:002' is a Canon LiDE 110 flatbed scanner
scanimage (sane-backends) 1.0.27; backend version 1.0.28
Scanner works locally on server (192.168.1.105), but does not work from a desktop on the LAN (192.168.1.106). I am unable to connect to port 6566 on the server via telnet. Connection closes immediately:
# telnet shuttle 6566
Trying 192.168.1.105...
Connected to shuttle.
Escape character is '^]'.
Connection closed by foreign host.
scanimage -L on the desktop fails to see the scanner
saned is running:
# systemctl status saned.socket
a- saned.socket - saned incoming socket
Loaded: loaded (/etc/systemd/system/saned.socket; enabled; vendor preset: disabled)
Active: active (listening) since Sun 2019-12-15 20:41:33 MST; 13h ago
Listen: [::]:6566 (Stream)
Accepted: 36; Connected: 0;
Memory: 128.0K
CGroup: /system.slice/saned.socket
Dec 15 20:41:33 shuttle systemd[1]: Listening on saned incoming socket.
saned.socket shows open and listening per other tools as well:
nmap -sV shuttle -p 6566
Starting Nmap 7.70 ( https://nmap.org ) at 2019-12-16 10:34 MST
Nmap scan report for shuttle (192.168.1.105)
Host is up (0.00015s latency).
PORT STATE SERVICE VERSION
6566/tcp open tcpwrapped
# netstat -l |grep sane-port
tcp6 0 0 [::]:sane-port [::]:*
my user is in the server's "scanner" group
saned is in "lp" group
Firewalls are down
/etc/saned/net.conf
## saned hosts
::1
localhost
192.168.1.106
192.168.1.105
/etc/hosts.allow is set for ALL:ALL
Does anybody have any ideas?
Thanks.
Mark