False alarm, problem solved. Devils in the details. On 2/8/07, Zate Berg <[EMAIL PROTECTED]> wrote:
A little background info. Previously I have been scanning from a Dual-Core Desktop running Ubuntu, Nessus 3.0.5, and NessusWX 1.4.5d. Everything was peachy. Recent changes required the scanning to be done from a certain location on the network and that location has only 2 windows servers in it, I cant justify deploying new hardware there right now. Installed 3.0.5 on a Windows 2003 server and had absolutely abysmal performance. My Desktop completed a scan in 15 minutes, the server took 2.5 hours. Exactly the same session from inside NessusWX. No amount of tweaking was able to make it run better on the Windows server. The windows server has 4 CPU's and 4 gb of Ram. My desktop has a single Dual Core and 2gb ram. I am now trying to run Nessus from a FC6 VMWare image. I know VMWare and Nessus aren't exactly scorching performers but I want to compare scan times with Nessus/FC6/VMWare vs Nessus/Win2k3/DL380. The issue I am having is the scan just completes in NessusWX with no results. Very quickly. nessusd.messages shows the client connect, says what hosts etc and then says completed. Nothing in nessusd.dump either. What else can I try to look at to see why this is happening ? -- Zate
-- Zate
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
