Tadaen_Sylvermane
May 4th, 2016, 07:17 PM
I've got my ltsp deployed and working quite nicely. Printing is working fine to my print server. I'm stuck on the scanner though. I'm trying to set it up to work over the network as it's an HP printer / scanner / copier.
Here is my files so far.
On Server:
jason@micromachine:~$ 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
In LTSP client chroot
jason@micromachine:~$ cat /opt/ltsp/amd64/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.240 # server hosting scanner
Googling is leading me to the same answers but nothing seems to be working. I know I'm overlooking something small. Ideas or suggestions, or request more config files to look at would be appreciated.
Here is my files so far.
On Server:
jason@micromachine:~$ 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
In LTSP client chroot
jason@micromachine:~$ cat /opt/ltsp/amd64/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.240 # server hosting scanner
Googling is leading me to the same answers but nothing seems to be working. I know I'm overlooking something small. Ideas or suggestions, or request more config files to look at would be appreciated.