Has anyone had a problem with 2.2.0 hanging when trying to scan a host
that was down? If I purposely put just one host as the target that does
not exist, it takes about 56 minutes for the tests to fail and Nessus to
return to a state that I can move around. If I have a list of hosts and
have a host in the middle that is down, Nessus hangs when it gets to
that host. Also, once it finally fails against the downed host, it
aborts the rest of the scans, saves what it haves and quits.
Any ideas?
Thanks,
Chris Sawall, GSEC, GSNA
Ameren
Information Security
*******************************
The information contained in this message may be privileged and/or confidential
and
protected from disclosure. If the reader of this message is not the intended
recipient,
or an employee or agent responsible for delivering this message to the intended
recipient,
you are hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited. Note that any views or opinions presented
in this
message are solely those of the author and do not necessarily represent those
of Ameren.
All emails are subject to monitoring and archival. Finally, the recipient
should check
this message and any attachments for the presence of viruses. Ameren accepts no
liability
for any damage caused by any virus transmitted by this email. If you have
received this in
error, please notify the sender immediately by replying to the message and
deleting the
material from any computer. Ameren Corporation
*******************************
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
