You are not logged in.

#1 2016-09-16 17:10:14

Janusz11
Member
Registered: 2007-05-16
Posts: 87

[SOLVED] Saned: client can't see scanner on host (scanner server)

I‘m trying to set up a scanner server. But by the power of Grayskull, I‘m unable to make the client find the scanner at the server.

On the server the scanner is found:

He-Man@banananas:~$ sudo sane-find-scanner

 # sane-find-scanner will now attempt to detect your scanner. If the
 # result is different from what you expected, first make sure your
 # scanner is powered up and properly connected to your computer.

 # No SCSI scanners found. If you expected something different, make sure that
 # you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x03f0 [HP], product=0xc611 [Officejet 4630 series]) at libusb:002:010
 # Your USB scanner was (probably) detected. It may or may not be supported by
 # SANE. Try scanimage -L and read the backend's manpage.

 # Not checking for parallel port scanners.

 # Most Scanners connected to the parallel port or other proprietary ports
 # can't be detected by this program.
He-Man@banananas:~$ sudo scanimage -L
device `hpaio:/usb/Officejet_4630_series?serial=CN517592W505Y0' is a Hewlett-Packard Officejet_4630_series all-in-one

Saned is configured to enable access for the clients on the network:

# saned.conf
# Configuration for the saned daemon

## Daemon options
# Port range for the data connection. Choose a range inside [1024 - 65535].
# Avoid specifying too large a range, for performance reasons.
#
# ONLY use this if your saned server is sitting behind a firewall. If your
# firewall is a Linux machine, we strongly recommend using the
# Netfilter nf_conntrack_sane connection tracking module instead.
#
# data_portrange = 10000 - 10100


## Access list
# A list of host names, IP addresses or IP subnets (CIDR notation) that
# are permitted to use local SANE devices. IPv6 addresses must be enclosed
# in brackets, and should always be specified in their compressed form.
#
# The hostname matching is not case-sensitive.

#scan-client.somedomain.firm
#192.168.0.1
#192.168.0.1/29
#[2001:db8:185e::42:12]
#[2001:db8:185e::42:12]/64

198.168.178.0/24

Saned is enabled and running and can be seen from the client:

Skeletor@archdesktop ~ % sudo nmap 192.168.178.10

Starting Nmap 7.12 ( https://nmap.org ) at 2016-09-16 18:48 CEST
Nmap scan report for 192.168.178.10
Host is up (0.0012s latency).
Not shown: 995 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
139/tcp  open  netbios-ssn
445/tcp  open  microsoft-ds
631/tcp  open  ipp
6566/tcp open  sane-port
MAC Address: 03:7G:08:B2:3C:A7 (Unknown)

Nmap done: 1 IP address (1 host up) scanned in 0.23 seconds

The net backend is enabled on the client:

# /etc/sane.d/dll.conf - Configuration file for the SANE dynamic backend loader
#
# Backends can also be enabled by configuration snippets under
# /etc/sane.d/dll.d directory -- packages providing backends should drop
# a config file similar to dll.conf in this directory, named after the package.
#

# The next line enables the network backend; comment it out if you don't need
# to use a remote SANE scanner over the network - see sane-net(5) and saned(8)
net

and the server IP address has been defined in the /etc/sane.d/net.conf file:

# This is the net backend config file.

## net backend options
# Timeout for the initial connection to saned. This will prevent the backend
# from blocking for several minutes trying to connect to an unresponsive
# saned host (network outage, host down, ...). Value in seconds.
# connect_timeout = 60

## saned hosts
# Each line names a host to attach to.
# If you list "localhost" then your backends can be accessed either
# directly or through the net backend.  Going through the net backend
# may be necessary to access devices that need special privileges.
# localhost
192.168.178.10

But when checking for the scanner on the client, the latter isn’t seeing it:

Skeletor@archdesktop ~ % sudo scanimage -L            

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

I’ve checked and read countless sources and how-to’s by now. But no matter what I do, the outcome is the same, the client does not find the scanner on the host.

I’m out of ideas now, so if anyone has one I’d be glad to give it a whirl.

Thanks in advance!


UPDATE

Problem solved. It turned out that only the sane daemon needed to be added to the lp group to give it access to the scanner. :-P

sudo adduser saned lp

Last edited by Janusz11 (2016-09-18 17:08:15)

Offline

Board footer

Powered by FluxBB