On Mon, 25 Nov 2002, Colette L'Heureux wrote:
> I recently ran nessus version 1.2.6 (all dangerous plug-ins disabled) against a
>server running the Job Scheduler called ESP. Nessus appears to have crashed this
>software products and I am trying to figure out why. I have no log files that
>indicate a problem with the software until 12 hours after the scan was run (when the
>next scheduled job tried to run). My admins are screaming at me that the non
>destructive scan caused destruction. Please help
In general. If you do not babysit the target machine you may always end up
with a machine that decides to call it a day.
At some time you may find that a scan reveals a weakness at a unlikely
spot as you just happened to do now. I once blew a E1 link out of action
as the Cisco router for that link was configured to log suspect traffic
and I hit it with several nmap session just to find that the router went
belly up.
Hugo.
--
All email sent to me is bound to the rules described on my homepage.
[EMAIL PROTECTED] http://hvdkooij.xs4all.nl/
Don't meddle in the affairs of sysadmins,
for they are subtle and quick to anger.
-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.
