On Mar 27, 2006, at 7:11 PM, Kenneth Shelton wrote:
We routinely scan our entire class B subnet monthly. As we are a
University, we are very compartmentalized and the scans are,
therefore, broken up into chunks. We have run into an issue that
the nessus client (ran from a seperate machine as the nessus
daemon) receives a connection termination from the nessus daemon in
the middle of most of the larger scans. Last month I tracked down
a specific scan that was giving us a problem and isolated the
problem to one class C which, when scanned even by itself would
still cause a crash the majority of the time, but it did actually
complete the scan once. Now about 5-7 blocks larger blocks are
crashing in the middle of the scans and the issue has us pooling
our hair out.
Here are the arguments being passed to the client:
nessus -V -q -T xml
Here is the output from the nessus daemon
secscan1 logs # nessusd -v
nessusd (Nessus) 2.3.1 for Linux
Nessus 2.3.x is highly unstable. I recommand upgrading to Nessus 3
which scales better when doing bigger scans.
-- Renaud
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
