Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Re: New Linux Server - nessusWX scans terminate with no info

Subject: Re: New Linux Server - nessusWX scans terminate with no info
Date: Thu, 8 Feb 2007 11:18:34 -0500
False alarm, problem solved.  Devils in the details.

On 2/8/07, Zate Berg <zate75@gmail.com> 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
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
<Prev in Thread] Current Thread [Next in Thread>