> Still, for increased performance and scan reliability, we recommend that you > use Nessus Windows on a server product such as Windows 2003 Server.
I just switched to Windows 2003, the behaviour of nessus looks more reliable (range was taken into account) However, afer 30 mn of testing and tricking, the "port scanner to use" in the option tab where all unselected, (on all the policies, event the default scan policy that I didn't use). I check again then the nessus TCP scanner, save and etc. then it stay checked But, again, Nessus ID : 19506 reports WARNING : no port scanner was enabled during the scan. This may lead to incomplete results If I save the session (.nessus) and then re-open the file, the port scanner to use are then again all unchecked. I spent a lot of time on this, it's driving me crazy Anyway, any help welcome, I'm currenlty evaluation solutions, I'd like to have this one working David > >>> If you're running under Windows, this is a known limitation >> >> Does this means that the nessus port scanner is not working on Windows >> ? Using the SYN scanner doesn't take into account the range port. > > I was wrong - apparently, Nessus Windows simulates the presence of the TCP > scanner but really uses the SYN scanner under the hood. > > George > -- > the...@tenablesecurity.com > > > > -- David ROBERT _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
