I am using Nessus Client v3.0.0 (build 2G161_Q) for the Windows scan. I
can try the new client and see if that makes a difference.
For the Linux command, I am using the following.
/opt/nessus/bin/nessus -c <path to nessusrc> -q localhost 1241 <User>
<Pass> <Target List> <Output>
Brock Tucker
-----Original Message-----
From: nessus-bounces@list.nessus.org
[mailto:nessus-bounces@list.nessus.org] On Behalf Of George A. Theall
Sent: Wednesday, February 20, 2008 3:46 PM
To: nessus@list.nessus.org
Subject: Re: no port scanner was enabled during the scan
On Feb 20, 2008, at 4:03 PM, Tucker, Brock - St. Louis, MO wrote:
I'm using nessus 3.0.6 on Linux RH ES5.
If I run a scan from the box using the command line, I get similar
results as listed below (no port scanner was enabled during the scan).
If I connect to the scanner from a windows client and create a new
policy, I can see that the scanner is enabled. When I run the scan
from
it, there are no issues. I've then tried exporting the policy from the
Windows client and using that on the command line in Linux. Result: no
port scanner was enabled during the scan.
Which client(s) are you using? And how are you invoking your
commandline scans?
There is a known issue with NessusClient 3.0.0 omitting the
SCANNER_SET section when exporting policies; eg, see:
http://list.nessus.org/pipermail/nessus-announce/2007-December/000003.ht
ml
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
