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: Running in command line

Subject: Re: Running in command line
Date: Thu, 21 Jul 2005 20:58:20 -0400
On Thu, Jul 21, 2005 at 01:24:00PM -0400, gmourani@privalodc.com wrote:

I've a problem with latest version of Nessus and any previous version too.
Presently I'm using version 2.2.5 

Sure about that version number?

Loaded Nessus daemon
without SSL support to avoid the steps to create certificate at this time,
and tested if I can connect to it localy and remotely, since now
everything is going well, I can connect localy or remotely. Therefore I
decided to start a scan on one host (172.16.1.1) and this take a days and
doesn't finish to execute. 

Have you altered the default .nessusrc file used for the scans? If so,
which port scanner(s) and port range are you using for the scan?

What appears in the nessusd.messages log when you launch a scan? What
processes related to nessusd exist when a scan appears to hang?


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>