On Wed, Aug 09, 2006 at 07:19:16PM -0500, Eric Whitehill wrote: > for some reason it is only performing > checks - it is not performing TCP scans. ... > [Wed Aug 9 18:55:51 2006][5239] user ewhitehill starts a new scan. Target(s) > : > x.x.x.x, with max_hosts = 20 and max_checks = 5 > [Wed Aug 9 18:55:51 2006][5239] user ewhitehill : testing x.x.x.x ) [3176] > [Wed Aug 9 18:55:55 2006][3176] user ewhitehill : launching > clrtxt_proto_settin > gs.nasl against x.x.x.x [3178] > [Wed Aug 9 18:55:55 2006][3176] user ewhitehill : launching > ssh_settings.nasl a > gainst x.x.x.x [3179]
The two plugins listed here are both in the ACT_INIT category and, as such, will always be run before any other plugins. What appears after these lines in the log (eg, the next 5 items)? > For scan options, I have Nessus SNMP, Netstat 'scanner', Nessus TCP > scanner, and Ping the remote host checked. What happens if you just use the Nessus TCP scanner? > Port range is set to the default. I think that means TCP ports 1-15000. If you don't need to scan so many ports, consider trimming it down. > Granted, I am still getting the results I want, however it is taking a > very long time (several hours to do a /24) and it's getting to be rather > frustrating. Go through the log file (nessusd.messages) to see which plugins are taking up the lion's share of the time. Also, have you chosen to optimize the scan (eg, "Optimize the test" in NessusClient)? George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
