Thanks for your reply, it was pretty much spot-on. I stopped using VMWare and started using a a real Fedora Core 5 box, and the problems have disappeared. Let it be a lesson to future virtualization users: the warning Nessus gives about abysmal performance also means abysmal results.

For future reference, I'm using VMWare Workstation 5.5.1 build-19175, VMWare tools installed, and networking handled through NAT.

--Andrew

On 7/16/06, George A. Theall <[EMAIL PROTECTED]> wrote:
On Fri, Jul 14, 2006 at 12:27:54PM -0400, Andrew Wang wrote:

> I've installed Nessus 3.0.3 and NessusClient on a Fedora Core 5 box
> running in VMWare (Windows XP host).
...
> Is this just a limitation of Nessus? I'm not changing any configuration
> options in between these scans except the target.

I doubt it's a limitation of Nessus per se, but it might be related to
the max_hosts setting currently in effect as well as where the targets
are located in relation to your nessusd host.

In addition, VMWare itself might be negatively affecting the results.


George
--
[EMAIL PROTECTED]
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to