On 10/05/07 07:34, Kevin Mc Grath wrote: > Nothing has been logged in the nessusd.dump file since last month.
What about something like a syslog file on the target? > The > Nessus policy that the device is subjected to is simple. The policy is > the default Nessus scan policy with "safe checks" disabled. You may want to limit your scan to individual ports, one at a time, you know are open and re-run the scans to get some idea of which service is causing the crash or whether it's a resource availability issue. Does enabling safe checks prevent the crash from happening? George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
