Did a similar installation a few months ago with openSuSE 11.0, which works fine on the same client machine.
This suggests you’re familiar with setting up scanners for remote access. I’ve never had to share a scanner from a Linux host, so I can’t offer as much help as I’d like to be able to. Anyway, to start with, you might want to post /etc/sane.d/saned.conf contents here. I know this is file needs to be correctly configured to allow remote scanner access first.
1] Is there anything I have missed?
2] Is anything known to be broken in 11.2?
3] Any other ides?
I assume you have the necessary services running on host:
Thanks for your reply! I am not terribly familiar with setting up scanners for network access, I mostly get by with a little help from my friends.
# 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.
# NOTE: /etc/inetd.conf (or /etc/xinetd.conf) and
# /etc/services must also be properly configured to start
# the saned daemon as documented in saned(8), services(4)
# and inetd.conf(4) (or xinetd.conf(5)).
Nothing remarkable, I think. Thanks for the link to the saned document - this fairly well confirms what I have done., I have checked through against what I have done and it seems fine - I have also checked against a known working installation and there appears to be no significant differences apart from the working installation being openSuSE 11.0.
1]:P:P:P:P Of course. Machines can see each other. I’m making that other mistake instead - remotely logging into the scanning server as root from the intended scanning client
3] Will check this and report back. I don’t think there is an issue here, because using xsane on the host machine shows the scanner twice - once as a directly connected usb scanner and again as a networkscanner on localhost. So it seems to be getting the scanner up on to TCP/IP
Thanks for input from all, some progress, but not yet complete
The clue was in /var/log/messages
*date host* saned[nnnn] : saned (AF-indep+IPv6) from sane-backends 1.0.20 starting up
*date host* saned[nnnn] : check_host: access by remote host: *IPv4 address*
*date host* saned[nnnn] : scheck_host: getaddrinfo for local hostname failed: Name or service not known
*date host* kernel: [nnnn.nnnnnn] saned[nnnn]: segfault at 28 IP b76d1a62 sp bfe5acec error 4 in linc-2.10.1.so [b761a000+159000]
just edited /etc/hosts on my scan server and added its own IP address and name, and now the scanner is visible to the client machine.
I am going to have a little root around, because I suspect the saned server is configured with its hostname rather than its IP address which it really needs.
Beyond that point, I now have the scanner pulling in pages and scanning - but not there yet, because the scan data is not returned to the client. Further ideas gratefully received.
just edited /etc/hosts on my scan server and added its own IP address and name, and now the scanner is visible to the client machine. I am going to have a little root around, because I suspect the saned server is configured with its hostname rather than its IP address which it really needs.
Well done DVardysShadow. Yes, for small networks without name servers, it is a good idea to declare your server’s IP and hostname in /etc/hosts (which is why I thought /var/log/messages might turn up something like the error you were getting).
You may have to adjust your firewall to allow for the random ports (above 1024) used for sane data as mentioned here: