On 09/19/07 13:12, Joel Elwell wrote: > I noted that the plugin "find_service.nasl" in version 3.0.3, indicates it's > meant to replace the > "find_service.nes". Which is actually running in my case? One or both?
find_service.nasl will replace the C-language plugin starting in Nessus 3.2. > For additional background info: The DoS target is a presentation layer > "service" providing SQL database > info from the back end to the application running in a browser session. Runs > on Windows Server 2003 and IIS. When you're running your scans and seeing CPU usage spike, you're enabling just #10330 for service detection, right? Is the target remote? What services are listening remotely? Which processes are using most of the CPU when the DoS occurs? George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
