Nessus
[Top] [All Lists]

Re: plugin 11475

To: nessus@list.nessus.org
Subject: Re: plugin 11475
From: "George A. Theall" <theall@tenablesecurity.com>
Date: Tue, 20 Feb 2007 21:09:55 -0500
Delivered-to: sp-com-lists@consult.net
Delivered-to: nessus-list1@securepoint.com
Delivered-to: nessus@list.nessus.org
In-reply-to: <45DB0E2A.2070603@st-tel.net>
List-archive: <http://mail.nessus.org/pipermail/nessus>
List-help: <mailto:nessus-request@list.nessus.org?subject=help>
List-id: Discussion of Nessus software <nessus.list.nessus.org>
List-post: <mailto:nessus@list.nessus.org>
List-subscribe: <http://mail.nessus.org/mailman/listinfo/nessus>, <mailto:nessus-request@list.nessus.org?subject=subscribe>
List-unsubscribe: <http://mail.nessus.org/mailman/listinfo/nessus>, <mailto:nessus-request@list.nessus.org?subject=unsubscribe>
References: <45DB0E2A.2070603@st-tel.net>
Sender: nessus-bounces@list.nessus.org
User-agent: Thunderbird 1.5.0.9 (X11/20061206)
On Tue, Feb 20, 2007 at 09:05:14AM -0600, Ward Taylor wrote:

When scanning a Sonicwall host using nessus for windows 3.0.5 several
plugins such as 11475 and 10134 report that the host has crashed even
though it does not.  Can something be done for this besides disabling
the affected plugins?

How are you determining the host hasn't crashed? Can you still route traffic through it during or shortly after a scan?

I don't have any direct experience with Sonicwalls, but looking back through the list archives shows the devices have not proven very robust when portscanned with Nessus or nmap in the past. Are you using an older device?

George
--
theall@tenablesecurity.com
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>