On Thu, Jan 29, 2004 at 09:52:16AM -0600, [EMAIL PROTECTED] wrote:
> Here's my issue. How do I determine within Nessus configuration (client
> side) which one of the plugins may have been responsible for this? I know
> I can go to the nessus site and get the code for these plugins but how do
> I determine which plugin might be affecting the system I'm running the
> scan against?
Usually, you'll want to launch the plugin one by one and add a sleep()
delay between two. The problem is that plugins with side effects are
usually hard to diagnose.
In your case, I'd suggest that the port scanner is actually the cause of
the problem. Try to re-scan with a syn scanner and see if the service
dies again (it should not)
-- Renaud
_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus
