http://bugzilla.novell.com/show_bug.cgi?id=551282
http://bugzilla.novell.com/show_bug.cgi?id=551282#c11
Joseph Short changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|pagan13@estreet.com |
--- Comment #11 from Joseph Short 2009-12-02 00:42:57 UTC ---
Sorry for taking so long, unavoidable circumstances. There is no test
procedure for the network connection in that web page, so I had to make up my
own using clues from the page and links from it.
Here is what I did:
In the web page, under network scanning/saned, I found a reference, in a
warning, to read "man saned"
Doing that, under "RESTRICTIONS" I found the line:
"In addition to the control connection (port 6566) saned also uses a data
connection. The port of this socket is selected by the operating system and
can't be specified by the user currently. This may be a problem if the
connection must go through a firewall (packet filter). If you must use a
packet filter, make sure that all ports > 1024 are open on the server for
connections from the client."
That reference to network ports gave me what I needed to experiment. This is
what I did next:
1. Opened tcp ports 1024-7999 on the server. (For some reason, I had 8000:8001
programmed into the manual tcp port list, even though I have http and https
server options enabled.)
Tried to scan, instead of "searching for scanner" dialog box hanging for a long
time, it came up immediately with a "scanner not found" message.
I then re-installed the scanner driver on the server.
Tried scanning again and the behavior of xsane reverted to its previous state:
hanging on the searching box before finally getting the not found error
message. I went back to the server and found that the tcp port setting changed
to 1024:6565 6567:8001. I reset ports to 1024:7999 8000:8001 and set the
allowed clients to 192.168.0.0/8 (from 127.0.0.0/8).
Tried another preview scan. The xsane dialog actually came up. I clicked the
acquire preview button and the scanner scanned, then hung.
I tried some more port settings, then just shut the firewall down. Ran full
scanning tests, and found all network scanning completely restored (remember,
FIREWALL OFF).
It appears the server firewall is not being set up properly to allow networked
scanning. In addition, it was actually altered during or by the update in such
a way as to break network scanning capability. That man page says there are
ports, for data use, that cannot be set by the user, and I can find no
reference to what they are.
I hope this helps.
--
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.