Sorry if this is not the right place to send this kind of problem.<br><br>I have a small network of computers at home. I just got an Epson V200 scanner and have been mostly successful in getting it running with "iscan" and "xsane" frontends (using the avasys proprietary driver and plugin). I can run the scanner from my athlon (32 bit) under ubuntu hardy locally and I can access it over the network from any of my other computers using saned.<br><br>If I connect the scanner directly to my amd64-x2 running ubuntu hardy (64) I can scan locally with "iscan" or "xsane" frontends (using the avasys proprietary driver and plugin) and using "libsane and sane-utils" for i386 (dpkg -i --force-all).<br><br>Now, if I run saned -d on the amd64-x2 I can connect from my other machines and run "iscan" or "xsane" frontends. Here is the output from the amd64-2 in this situation <br><br>++++++++++++++++++++++++++++++++++++++++++++<br>gregg@g2-xubuntu:/etc/init.d$ scanimage
-L<br>[sanei_debug] Setting debug level of dll to 0.<br>[sanei_debug] Setting debug level of net to 128.<br>[net] sane_init: authorize = 0x804ae30, version_code = 0xff962508<br>[net] sane_init: SANE net backend version 1.0.14 (AF-indep+IPv6) from sane-backends 1.0.18-cvs<br>[net] sane_init: Client has little endian byte order<br>[net] sane_init: searching for config file<br>[net] sane_init: trying to add 192.168.1.25<br>[net] add_device: adding backend 192.168.1.25<br>[net] add_device: backend 192.168.1.25 added<br>[net] sane_init: done reading config<br>[net] sane_init: evaluating environment variable SANE_NET_HOSTS<br>[net] sane_init: evaluating environment variable SANE_NET_TIMEOUT<br>[net] sane_init: done<br>[net] sane_get_devices: local_only = 0<br>[net] connect_dev: trying to connect to 192.168.1.25<br>[net] connect_dev: [0] connection succeeded (IPv4)<br>[net] connect_dev: sanei_w_init<br>[net] connect_dev: net_init (user=gregg, local version=1.0.3)<br>[net]
connect_dev: freeing init reply (status=Success, remote version=1.0.3)<br>[net] connect_dev: done<br>[net] sane_get_devices: got 192.168.1.25:epkowa:libusb:001:002<br>[net] sane_get_devices: finished (1 devices)<br>device `epkowa:libusb:001:002' is a Epson Perfection V200 flatbed scanner<br>device `net:192.168.1.25:epkowa:libusb:001:002' is a Epson Perfection V200 flatbed scanner<br>[net] sane_exit: exiting<br>[net] sane_exit: closing dev 0x8065748, ctl=3<br>[net] sane_exit: finished.<br><br>++++++++++++++++++++++++++++++++++++++++<br><br>Great! The epkowa and net devices are listed as you can see.<br><br><br>Now if I start xinetd and try again, this is what I get.<br><br><br>%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%<br>gregg@g2-xubuntu:/etc/init.d$ scanimage -L<br>[sanei_debug] Setting debug level of dll to 0.<br>[sanei_debug] Setting debug level of net to 128.<br>[net] sane_init: authorize = 0x804ae30, version_code = 0xffb67f18<br>[net] sane_init: SANE net backend version 1.0.14
(AF-indep+IPv6) from sane-backends 1.0.18-cvs<br>[net] sane_init: Client has little endian byte order<br>[net] sane_init: searching for config file<br>[net] sane_init: trying to add 192.168.1.25<br>[net] add_device: adding backend 192.168.1.25<br>[net] add_device: backend 192.168.1.25 added<br>[net] sane_init: done reading config<br>[net] sane_init: evaluating environment variable SANE_NET_HOSTS<br>[net] sane_init: evaluating environment variable SANE_NET_TIMEOUT<br>[net] sane_init: done<br>[net] sane_get_devices: local_only = 0<br>[net] connect_dev: trying to connect to 192.168.1.25<br>[net] connect_dev: [0] connection succeeded (IPv4)<br>[net] connect_dev: sanei_w_init<br>[net] connect_dev: net_init (user=gregg, local version=1.0.3)<br>[net] connect_dev: freeing init reply (status=Unknown SANE status code 1667329132, remote version=105.110.26400)<br>[net] connect_dev: access to 192.168.1.25 denied<br>[net] connect_dev: closing connection to 192.168.1.25<br>[net]
sane_get_devices: ignoring failure to connect to 192.168.1.25<br>[net] sane_get_devices: finished (0 devices)<br>device `epkowa:libusb:001:002' is a Epson Perfection V200 flatbed scanner<br>[net] sane_exit: exiting<br>[net] sane_exit: closing dev 0x8065748, ctl=-1<br>[net] sane_exit: finished.<br><br><br>%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%<br><br>[net] connect_dev: freeing init reply (status=Unknown SANE status code 1667329132, remote version=105.110.26400)<br><br>This doesn't look good to me. I am guessing this is a problem with my xinetd.conf setup, permissions, or something like that and not actually a problem with saned. Am I on the right path?<br><br>This is my xinetd.conf<br><br># Simple configuration file for xinetd<br>#<br># Some defaults, and include /etc/xinetd.d/<br><br>defaults<br>{<br><br># Please note that you need a log_type line to be able to use log_on_success<br># and log_on_failure. The default is the following :<br># log_type = SYSLOG daemon
info<br><br>}<br><br><br> # default: off<br> # description: The sane server accepts requests<br> # for network access to a local scanner via the<br> # network.<br> service sane-port<br> {<br> port = 6566<br> socket_type =
stream<br> wait = no<br> user = saned<br> group = scanner<br> server = /usr/sbin/saned<br> }<br><br>I have tried group = scanner and group = saned, but neither one works.<br><br>Any suggestions? Thanks in advance!<br><br><br><br>