Thanks to those that have replied. I have decided to update my post so as
to be more specific.
I am running nessusd 1.0.10 with the linux nessus client v. 1.0.10, which
is the standard apt package for nessus in debian 3.0 unstable. I am able
to connect to the server with the client running on the same machine. Up
until a week ago I was able to connect, with WinNessus 1.0.9 from the
machines filtered in through hosts.allow, in essentially the same way that
I have sshd managed. NOTE: the machines unable to connect to nessus CAN
connect to sshd.
I have tried using WXNessus, even though the version of nessud I am using
does not warrant that. I suspect that the connection is being blocked
even before the remote client can communicate with nessusd. So the
question here is more directed to what could be stopping the connection
from completing rather than what could be wrong with nessusd.
Thank you all for your patience.
josh bauman
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Joshua Bauman - GNU Crusader
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED]
www.darw1n.net
, ,
/ \
((__-^^-,-^^-__)) _____
`-_---' `---_-' / \
`--|o` 'o|--' | w3rd! |
\ ` / \___ _/
): :( )/
:o_o:
"-"
