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. |

| Subject: | Re: problem running nessus |
|---|---|
| Date: | Thu, 5 Jul 2007 10:17:16 -0700 |
So let me re-phrase my question. The only reason I even mentioned
port=scanned was because it was the first thing my eyes locked onto when I
wrote the email. Let port-scanning out for the moment, because I don't
have the NMAP plug-in loaded. Running NessusWX from my windows client,
the only IP that seems to get a legitimate treatment from the nessus
server is my NessusWX host (I get similar results running the Tenable
client). All of the rest immediately display 100% of tests run and I get
0 holes, 0 warnings, 0 info etc. I know this isn't right because this
network has more holes than Swiss cheese.
The server is a vanilla instance of Gentoo, so while it's possible
something is filtering it "out of the box", I don't think that is the
case. The nessus.messages file is empty.
Thanks
-Joshua Sanders
jsanders@westernmutual.com
"George A. Theall" <theall@tenablesecurity.com>
Sent by: nessus-bounces@list.nessus.org
07/03/2007 07:01 PM
To: nessus@list.nessus.org
cc:
Subject: Re: problem running nessus
On 07/03/07 18:52, JSanders@westernmutual.com wrote:
When I scan the subnet my client software is running on, it finds all the machines in the results,
but the only one that get's portscanned and has any information on is my
client machine. The same thing happens if I scan the subnet where the nessus server is located. I only get results on the server machine and nothing else in the subnet.
Which port scanners have you enabled and how are they configured? And what range of ports are you scanning? What if anything appears in the nessusd.messages log file when you run a scan? Is there anything that might be filtering traffic to/from the Nessus server host? Btw, if you used the 2.2.6 ebuild, you may want to consider upgrading to 2.2.10 (if you build from source) or 2.2.9 (using emerge): http://mail.nessus.org/pipermail/nessus-announce/2007-May/msg00000.html George -- theall@tenablesecurity.com _______________________________________________ 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
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Red Hat Enterprise 5, Patrick S. Harper |
|---|---|
| Next by Date: | Re: problem running nessus, jfvanmeter |
| Previous by Thread: | Re: problem running nessus, George A. Theall |
| Next by Thread: | Re: problem running nessus, Michel Arboi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |