I've been a nessus user for years, but I have getting horrible results recently when scanning more than one host at a time.
When scanning multiple hosts, the scanner will completely miss open ports, or it will see the port as open during the port scan, but then report that the port "was open but is now closed". I have had this problem on numerous installations recently, all using the latest rpm for suse 10 and the latest nessus-client version. The scans I am performing are using the default scan policy, the default port range, and the default scan options. If I scan one host at a time I get "more reliable" results. Although I'm questioning any results I get. And scanning a class C is very time consuming when starting one host at a time. Not sure if anyone else has had issues and/or has any ideas. Oh, and my hardware is new too so I don't think its a processor/memory problem. Thanks for any feedback. I sure hope I'm missing something easy.
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
