http://bugzilla.novell.com/show_bug.cgi?id=551282
http://bugzilla.novell.com/show_bug.cgi?id=551282#c12
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
Summary|After whatever software |After whatever software
|update network scanning |update the firewall runs
|broken |which made scanning via
| |network impossible
--- Comment #12 from Johannes Meixner 2009-12-02 08:35:29 UTC ---
So in the end it was a running firewall which
made network scanning impossible.
This is no bug regarding scanning.
This is documented in the YaST scanner setup help text
and therein you can also disable firewall protection
for the 'INT' zone (but only if you use the SuSEfirewall):
------------------------------------------------------------------
Scanning via Network
..
Server Settings
If you have locally connected scanners and want
to make them accessible via the network,
set up the saned network scanning daemon
so that your host becomes a server.
In 'Permitted Clients', enter which client hosts
are permitted to access saned on your server.
Enter a comma-separated list of client hosts
(hostnames or IP addresses) or subnets
(CIDR notation, such as 192.168.1.0/24).
If no client hosts are permitted, saned is not activated.
If saned is activated, xinetd is also activated
and set up for saned.
Clients contact saned via the sane-port (TCP port 6566)
but scanning data is transferred via an additional random port.
The default 'Firewall Settings' during system installation
protect your host from external access.
This is not a problem when using scanners in an internal network
(when the network interface belongs to the internal network zone)
unless you have firewall protection enabled for the internal zone.
Allowing access from an external network does not make sense
because scanning documents requires physical scanner access.
Therefore access from the external zone can only be denied
if it was accidentally allowed by insecure firewall settings.
..
Client Settings
If you want to access scanners connected to other hosts (servers)
in the network, set up the net metadriver to access them via
the daemon running on the servers.
saned and firewall on the servers must permit the access.
In 'Servers Used', enter which servers should be used.
Enter a comma-separated list of servers (server names
or IP addresses).
If no servers are entered, net is not activated.
------------------------------------------------------------------
It seems the bug here is that somehow (I have no idea how)
the firewall was activated after whatever software update.
If you may find out what caused this, you may file a new
bug report regarding the comonent which seems to have
activated the firewall after whatever software update.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.