are you running a administrative scan?
nessus also needs rights to make a remote connection to the registry, so the
account your using for your nessus scan have admin rights to the servers your
scanning?
--John
-------------- Original message ----------------------
From: [EMAIL PROTECTED]
> 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
> [EMAIL PROTECTED]
>
>
>
>
>
>
> "George A. Theall" <[EMAIL PROTECTED]>
> Sent by: [EMAIL PROTECTED]
> 07/03/2007 07:01 PM
>
> To: [email protected]
> cc:
> Subject: Re: problem running nessus
>
>
> On 07/03/07 18:52, [EMAIL PROTECTED] 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
> --
> [EMAIL PROTECTED]
> _______________________________________________
> Nessus mailing list
> [email protected]
> http://mail.nessus.org/mailman/listinfo/nessus
>
>
--- Begin Message ---
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
[EMAIL PROTECTED]
"George A. Theall" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
07/03/2007 07:01 PM
To: [email protected]
cc:
Subject: Re: problem running nessus
On 07/03/07 18:52, [EMAIL PROTECTED] 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
--
[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
--- End Message ---
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
