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.html George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
