Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Re: Strange Nessus Behavior

Subject: Re: Strange Nessus Behavior
Date: Wed, 20 Dec 2006 20:21:02 -0500
On Wed, Dec 20, 2006 at 12:09:32PM -0500, Steven Adair wrote:

> I also cannot seem to find
any option to make this a default setting in nessusd.conf to consider the
unscanned ports as closed.  Is there a way to do this?

"unscanned_closed = yes" should work.

Subsequently this brings us to another issue we've had with Nessus as of
late. Starting a month or so ago when trying to start a scan with an of
the *nix clients it just freezes and nothing happens.

Do you authenticate before trying to start a scan? What if anything is being written to the nessusd.messages logfile? Do you see any packets passing between the server and client? What processes related to nessusd are running?


George
--
theall@tenablesecurity.com
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>