maybe looking at ~/.nessusrc, the lines about options for performing a ping to the target ...
Tony Chang wrote: > Hey guys, > > I'm currently using nessus 2.2.3 on Linux, and I'm having kind of a > strange issue. > > When I initiate a remote IP scan, the scan always completes within > a few seconds and the output is always empty. > > Scan Details Hosts which were alive and responding during test 0 > > I assume the second line is the actual reason why there was no > output, but in this case I tried to initiate a scan on 127.0.0.1. I > don't think the problem is with nessusd necessarily, due to the > following in nessusd.messages: > > [Wed Jun 8 11:00:17 2005][1074] user scan starts a new scan. > Target(s) : 127.0.0.1, with max_hosts = 20 and max_checks = 4 [Wed > Jun 8 11:00:17 2005][1074] user scan : testing 127.0.0.1 > (127.0.0.1) [1075] [Wed Jun 8 11:00:17 2005][1074] user scan : > test complete [Wed Jun 8 11:00:17 2005][1074] user scan : Kept > alive connection > > This to me means that nessusd handled its part of the process > correctly, but the nessus client, due to some sort of health check > failing, determined that no attack scripts be executed on the host > in question. Am I wrong in my assumption, and has anyone else seen > this (hopefully fixed it)? > > Thanks, > > Tony _______________________________________________ Nessus mailing > list [email protected] > http://mail.nessus.org/mailman/listinfo/nessus > > _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
