I'm having trouble networking my scanner

TSquaredF · 04-17-2009, 01:09 PM

When I set it up on a client, it is found by "sane-find-scanner" & "scanimage -L" (as both root & a user). It works fine with xsane & skanlite (I installed KDE4 on this 12.2 installation back when that could be done & haven't changed anything since).
When I set it up on a server, "sane-find-scanner" & "scanimage -L" work fine & although I have no GUI environment on the server, I can do simple scans with scanimage.
On the server, I have the following:

Code:

cat /etc/services | grep sane
sane-port	 6566/tcp   #SANE network scanner daemon

Code:

cat /etc/inetd.conf | grep sane
sane-port  stream  tcp  nowait  saned:saned /usr/sbin/saned saned

Code:

# cat /etc/sane.d/saned.conf
#
# saned.conf
#
# The contents of the saned.conf  file  is  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.
#
desktop # hostname of the client
# 192.168.0.0/24 #I have tried this instead of the above line. Same results.
#
# 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)).

On both the server & the client, I have added a "saned" user & group (the "saned" user is the only member of this group & I have also added it as a member of the scanner group). This may not be necessary on the client, but I thought I'd try it.
On the client, I have

Code:

# cat /etc/sane.d/net.conf
# This is the net backend config file.
192.168.0.10 # server IP
# k5ttf # server hostname (I've tried both IP & hostname; same results)

Code:

# cat /etc/sane.d/dll.conf
# enable the next line if you want to allow access through the network:
net
epson2

Now, per the documentation I've read, "sane-find-scanner" should not work on the client, but "scanimage -L" should. Neither show a scanner.
I checked this post & my user belongs to both "lp" & "scanner" groups.
What have I done wrong?
Regards,
Bill

justwantin · 04-17-2009, 03:25 PM

You did not mention which version of Slackware you are using, my server is still 12.1.

Your server configs are the same as mine except I listed each client IP separately as there are only wanting the scanner

Your two client configs are basically the same as mine.

You said you could do simple scans on the server CLI, did you do that as root or a user. The reason I ask is that you did not say whether the user was made a member of the group lp on the server or the client or both. When I set up the server with 12.1, a client could not scan unless the user was a member of lp on the server.

TSquaredF · 04-17-2009, 04:51 PM

Quote:

You did not mention which version of Slackware you are using, my server is still 12.1.

12.2, but cut way down. No X, XAP, or a lot of the other packages. It is now just a backup/nfs/samba server, but I'm wanting to add scanner/printer services to it.

Quote:

You said you could do simple scans on the server CLI, did you do that as root or a user.

Both, my user is a member of the same groups on each machine.
The one thing I have noticed that is different is the way the scanner is listed in "scanimage -L". Your result for "scanimage -L" is

Quote:

device `net:192.168.1.4:hpaio:/usb/PSC_2350_series?serial=MY493C10JCKJ' is a Hewlett-Packard PSC_2350_series all-in-one

While I have not gotten the net to work, the format of my results on the server is

Quote:

device 'epson2:libusb:001:002' is a Epson GT-9300 flatbed scanner

There is a device for the scanner:

Quote:

# ls -l /dev | grep scan
crw-rw-r-- 1 root scanner 189, 1 2009-04-17 16:16 usbdev1.2

Could the way scanimage & the GUI programs are naming it be the problem?
Regards,
Bill

mrclisdue · 04-17-2009, 04:54 PM

The only difference I can see between what you have, and what I have, is that in the client's /etc/sane.d/net.conf file, I have included localhost, the server's hostname, the server's ip, and the whole subnet (192.168.1.0/24 (perhaps looking down the road to adding additional scanners to other boxes)). I, obviously, can't definitively say that this is what *makes* my setup work....

Other than that, it would appear that you've taken the same steps I took a few months back when I configure my setup.

EDIT: I'm just going over my setup, and I noticed in your original post that you had added 'saned' to the scanner group on your client. Is your user a member of the scanner group?

EDIT2: Have you tried invoking saned, /usr/sbin/saned, with -d and -s flags? I seem to recall making some headway in the past when I was stumped.

cheers,

justwantin · 04-17-2009, 05:10 PM

I gotta go to work so this is quick:

Quote:

root@box:/# scanimage -L
device `hpaio:/usb/PSC_2350_series?serial=MY493C10JCKJ' is a Hewlett-Packard PSC_2350_series all-in-one

but I get nada for devices:

Quote:

root@box:/# # ls -l /dev | grep scan
root@box:/#

Off the top of my head, note that on my server I have hpaio listed.

Quote:

12.2, but cut way down. No X, XAP, or a lot of the other packages

So do you have the relevant hp packages installed?

BCarey · 04-17-2009, 06:07 PM

In your inetd.conf, try "saned.saned" instead "saned:saned", ie. use a period instead of a colon. Don't forget to restart inetd after the change.

Brian

TSquaredF · 04-17-2009, 08:29 PM

mrclisdue: I set up my /etc/sane.d/saned.conf just like yours. No help. My user is in the scanner group on both computers.
I haven't yet tried to start saned outside of inetd, but will later tonight.
justwantin: This is an Epson scanner. I don't think the HP stuff will help.
BCarey: I tried your suggestion, but no help.
I still think it has something to do with me not having a usb filesystem, but I'm no where near sure.
Regards,
Bill

justwantin · 04-18-2009, 04:39 AM

Quote:

This is an Epson scanner

oops! I just returned home my mistake re: hpaio

TSquaredF · 04-19-2009, 07:13 AM

Well, I thought I'd found it, but no joy. I didn't have the "/etc/services" line on the client. I added it, but still no luck as either root or a user. Per the man-sane manpage, "the default host is the last host listed in the configuration file...". My client configuration file is:

Quote:

$ cat /etc/sane.d/net.conf
# This is the net backend config file.
localhost
192.168.0.10 # server IP
192.168.0.0/24
k5ttf # server hostname

I have rotated all four entries through the last position, again with no joy. Any other suggestions?
Regards,
Bill

mrclisdue · 04-19-2009, 09:48 AM

I suspect that saned isn't even running on the server. If you edit /etc/sane.d/net.conf on the server, and remove the comment beside localhost, then $ scanimage -L on the server should show two scanners: one available locally and directly, and the same one available through the net backend:

Code:

mrclisdue@spare_room:~$ scanimage -L
device `plustek:libusb:001:004' is a Canon CanoScan LiDE25 flatbed scanner
device `net:localhost:plustek:libusb:001:004' is a Canon CanoScan LiDE25 flatbed scanner

What are the results of

Code:

$ /usr/sbin/saned -d12

?

You should get sufficient output to stderr to debug the issue. When you attempt to connect to saned from either the client, or the server itself (if you have edited net.conf on the server), you should be able to see *something*, and then saned will exit.

cheers,

TSquaredF · 04-20-2009, 10:21 AM

mrclisdue:

Quote:

What are the results of

$ /usr/sbin/saned -d12 ?

Thanks a lot. Here is my first real clue. Those results

Code:

[saned] main: starting debug mode (level 12)
[saned] main: trying to get port for service 'sane-port' (getaddrinfo)
[saned] main: [0] socket () using IPv6
[saned] main: [0] setsockopt ()
[saned] main: [0] bind () to port 6566
[saned] main: [0] listen ()
[saned] main: [1] socket () using IPv4
[saned] main: [1] setsockopt ()
[saned] main: [1] bind () to port 6566
[saned] main: [1] bind failed: Address already in use
[saned] main: waiting for control connection

My assumption here is that I will have to turn off the IPv6 binding in order to let the IPv4 binding work. I don't currently know how to do that, but will find out.
Regards,
Bill

mrclisdue · 04-20-2009, 09:37 PM

Quote:

Originally Posted by TSquaredF

...My assumption here is that I will have to turn off the IPv6 binding in order to let the IPv4 binding work. I don't currently know how to do that, but will find out.

No!

You're fine, thus far. saned is waiting for a connection, which is what we want.

It's at this point that you should try to connect with either a client, or with your server (providing that you have uncommented 'localhost' from net.conf).

It's the next message, or lack thereof, that will help determine where the problem lies.

So, from either client or server, issue the command $ scanimage -L, and let's see what happens...

cheers.

TSquaredF · 04-22-2009, 08:54 AM

Thank you, mrclisdue, for hanging in here with me. I went back to the original setup: sane via inetd, IPv6 not blacklisted, "localhost" & "net" the only entries in net.conf. At that point, I ran "scanimage -L" & got:

Code:

device `epson2:libusb:001:002' is a Epson GT-9300 flatbed scanner

No response from the network side, so I removed sane from inetd.conf, restarted rc.inetd & entered (as root):

Code:

saned -d12 &

This gave me the same output as posted above in #11. At that point, I ran "scanimage -L" again & received exactly the same results as above. No response from the network side & no errors.
If this scanner didn't work flawlessly on both computers (locally), I would consider using a big ball-peen hammer next.
Regards,
Bill

mrclisdue · 04-22-2009, 11:17 AM

This could indicate that the issue is with the saned.conf file, which *tells* saned which hosts may access the scanner.

So, keep desktop, uncomment the subnet, and add the individual ip's of the server and client. For good measure, also add localhost and 127.0.0.1

I'll keep an eye out for ball peen hammer sales.

cheers,

magpieiain · 09-27-2009, 08:36 AM

I am having a similar problem...when I run saned -r then my scanner is recognised from the client - either using xsane or scanimage -L. However if I try either without running saned -d then the scanner is not recognised.

So if I d saned -d12 on the server I get:

Quote:

[saned] main: starting debug mode (level 12)
[saned] main: trying to get port for service `sane-port' (getaddrinfo)
[saned] main: [0] socket () using IPv6
[saned] main: [0] setsockopt ()
[saned] main: [0] bind () to port 6566
[saned] main: [0] listen ()
[saned] main: [1] socket () using IPv4
[saned] main: [1] setsockopt ()
[saned] main: [1] bind () to port 6566
[saned] main: [1] bind failed: Address already in use
[saned] main: waiting for control connection

To begin with. Then on the client scanimage -L gives:

Quote:

device `net:jervis:gt68xx:libusb:001:002' is a Genius Colorpage Vivid 1200 XE flatbed scanner

And then on the server the remainder of the 'saned -r12' message is:

Quote:

[saned] saned (AF-indep+IPv6) from sane-backends 1.0.19 ready
[saned] check_host: detected an IPv4-mapped address
[saned] check_host: access by remote host: ::ffff:192.168.0.6
[saned] check_host: remote host is not IN_LOOPBACK nor IN6_LOOPBACK
[saned] check_host: local hostname: jervis
[saned] check_host: local hostname(s) (from DNS): jervis
[saned] check_host: local hostname(s) (from DNS): (null)
[saned] check_host: local hostname(s) (from DNS): (null)
[saned] check_host: remote host doesn't have same addr as local
[saned] check_host: opening config file: /etc/hosts.equiv
[saned] check_host: can't open config file: /etc/hosts.equiv (No such file or directory)
[saned] check_host: opening config file: saned.conf
[saned] check_host: config file line: `#'
[saned] check_host: config file line: `# saned.conf'
[saned] check_host: config file line: `#'
[saned] check_host: config file line: `# The contents of the saned.conf file is a list of host names, IP'
[saned] check_host: config file line: `# addresses or IP subnets (CIDR notation) that are permitted to use local'
[saned] check_host: config file line: `# SANE devices. IPv6 addresses must be enclosed in brackets, and should'
[saned] check_host: config file line: `# always be specified in their compressed form.'
[saned] check_host: config file line: `#'
[saned] check_host: config file line: `# The hostname matching is not case-sensitive.'
[saned] check_host: config file line: `#'
[saned] check_host: config file line: `#scan-client.somedomain.firm'
[saned] check_host: config file line: `# localhost'
[saned] check_host: config file line: `# 127.0.0.1'
[saned] check_host: config file line: `192.168.0.1/29'
[saned] check_host: subnet with base IP = 192.168.0.1, CIDR netmask = 29
[saned] check_host: access granted from IP address 192.168.0.6 (in subnet 192.168.0.1/29)
[saned] init: access granted
[saned] init: access granted to iain@::ffff:192.168.0.6
[saned] process_request: waiting for request
[saned] process_request: got request 1
[saned] process_request: waiting for request
[saned] process_request: got request 10
[saned] quit: exiting

If I start and stop inetd using 'sudo service inetutils-inetd restart
' and then do 'Scanimage -L' from the client I get..

Quote:

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).

Now my inetd.conf file is as follows:

Quote:

#<off># netbios-ssn stream tcp nowait root /usr/sbin/tcpd /usr/sbin/smbd
sane-port stream tcp nowait saned.saned /usr/sbin/saned saned

I am guessing that the problem is in here somewhere, possibly with inetd, but I am not sure where. Please can somebody help with some suggestions? I am using Ubuntu 8.04 server.

Thanks,

Iain