Jesse, Are you running the scan from a command prompt using a .nessusrc policy file that was created in the Nessus GUI client and exported? If you did, chances are that the SCANNER_SET section within the .nessusrc file is not being written during the export process. This happened to me in version 3.0.6 and was supposed to be fixed in the current version of Nessus. I resolved the issue by manually going into the .nessusrc policy file and adding this section:
begin(SCANNER_SET) 10180 = no 10277 = no 10278 = no 10331 = no 10335 = yes 10841 = no 10336 = no end(SCANNER_SET) Hope this helps. Richard -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Saturday, June 21, 2008 12:00 PM To: [email protected] Subject: Nessus Digest, Vol 56, Issue 18 Send Nessus mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://mail.nessus.org/mailman/listinfo/nessus or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of Nessus digest..." Today's Topics: 1. WARNING : no port scanner was enabled during the scan. This may lead to incomplete results. (Jesse Mauntel) ---------------------------------------------------------------------- Message: 1 Date: Fri, 20 Jun 2008 13:57:39 -0700 From: "Jesse Mauntel" <[EMAIL PROTECTED]> Subject: WARNING : no port scanner was enabled during the scan. This may lead to incomplete results. To: <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" We just rebuilt our Nessus server as a RHEL 5 system and upgraded Nessus from 3.0.6 to 3.2.1. Now when we initiate a scan from our other system (client) we get the following message in our results: WARNING : no port scanner was enabled during the scan. This may lead to incomplete results. What causes this? Is there any way to correct it without upgrading the Nessus client? Thanks, - Jesse -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.nessus.org/pipermail/nessus/attachments/20080620/a2bbe496/at tachment-0001.html ------------------------------ _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus End of Nessus Digest, Vol 56, Issue 18 ************************************** _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
