Hi Steve, Is your SuSE Nessus scanner running natively on your laptop or is it running in a VM of some sort?
Are you scanning over wireless, through a firewall (either on your machine or your network), through a NAT or so on? Is there an IPS in the middle that is preventing Nessus from performing a scan? Are the targets you are scanning very busy, VM images or in any other way having I/O, CPU or memory usage issues during the scan. Scanning a host that periodically goes to 100% CPU usage won't return reliable port scans or scan results. During the scan, does your laptop experience high CPU usage or high memory usage? Ron Gula Tenable Network Security Steve Templists wrote: > 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 _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
