Nach dist-upgrade: Scannen über's Netzwerk kaputt
Hallo,
nach dem dist-upgrade von Lenny nach Squeeze geht bei mir das Scannen
über das Netzwerk nicht mehr. Das Scannen auf der Maschine, an der der
Scanner hängt, funktioniert. Unter Lenny hat das alles funktioniert.
Kann mir bitte jemand helfen, das wieder ans Laufen zu bekommen?
Auf dem Server:
Die saned.conf enthält nur eine unkommentierte Zeile:
8<-------------------------------
192.168.1.0/24
8<-------------------------------
/etc/services enthält u.a.:
sane-port 6566/tcp sane saned # SANE network scanner daemon
$ grep sane /etc/inetd.conf
sane-port stream tcp nowait saned.saned /usr/sbin/saned saned
$ sane-find-scanner
found USB scanner (vendor=0x03f0 [HP], product=0x2a12 [Officejet J4500
series]) at libusb:002:002
$ SANE_DEBUG_NET=128 scanimage -L
[sanei_debug] Setting debug level of net to 128.
[net] sane_init: authorize = 0x804d4a0, version_code = 0xbfe6d47c
[net] sane_init: SANE net backend version 1.0.14 (AF-indep+IPv6) from
sane-backends 1.0.21
[net] sane_init: Client has little endian byte order
[net] sane_init: searching for config file
[net] sane_init: done reading config
[net] sane_init: evaluating environment variable SANE_NET_HOSTS
[net] sane_init: evaluating environment variable SANE_NET_TIMEOUT
[net] sane_init: done
[net] sane_get_devices: local_only = 0
[net] sane_get_devices: finished (0 devices)
[net] net_avahi_browse_callback: CACHE_EXHAUSTED
device `hpaio:/usb/Officejet_J4500_series?serial=CN9CMD11BT052T' is a
Hewlett-Packard Officejet_J4500_series all-in-one
[net] sane_exit: exiting
[net] net_avahi_cleanup: stopping thread
[net] net_avahi_cleanup: done
[net] sane_exit: finished.
$ cat /etc/default/saned
# Defaults for the saned initscript, from sane-utils
# Set to yes to start saned
RUN=yes
# Set to the user saned should run as
RUN_AS_USER=saned
Auf dem Client:
$ cat /etc/sane.d/net.conf
# 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.1.29
$ 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).
$ groups
user lp dialout cdrom floppy audio video plugdev netdev fuse scanner
davfs2 saned
Reply to: