Re: Nessus taking a long time to scan

If your target machines are running or behind a firewall that DROPs packets
instead of REJECTs (that is, it doesn¹t respond back to the source machine
that it¹s packets have been rejected, but instead silently drops them), you
can see this behavior. I¹m not sure what the default behavior on windows
2003 is, but it wouldn¹t surprise me if it was dropping them. Our experience
shows that silently dropping the packets makes the nessus scanner think that
no one is live on the other end, so it times out every single plugin
attempt, prolonging your scan. Hyper-paranoid linux/OS X/BSD admins become
the bane of the scanner :)


On 9/23/05 1:33 PM, "Kelly, Jim" <Jim_Kelly@sra.com> wrote:

> I just want to get everyone's feedback:
> Nessus is currently up to 9333+ plugins
>
> Even with all the irrelevant plugins unchecked...like slackware, freebsd,
> solaris checks etc.
> Network only has windows 2003
> total of 60 hosts
> It's taking me 5-7 hours.
> I'm using three laptops
>  one C800 Dell
>  one D600 Dell
>  one Compaq Presario R3000.
>
> Is this typical for you all?
>
> What hardware specs would you recommend these days? Seems like the number of
> plugins (total) has doubled n the past 7 months...windows only maybe x2.5 or
> x3?
>
> Jim 
>
>
> _______________________________________________
> Nessus mailing list
> Nessus@list.nessus.org
> http://mail.nessus.org/mailman/listinfo/nessus


_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus