Nessus Scanner Protocol Error
Contents |
Post #1 of 9 (2199 views) Permalink nessus3 annoyances/wish list I'm sure this has been answered before, but an inability to security center scanner protocol error find it brought me here. Ubuntu 7.4 Nessusd 3.0.6 NessusClient 3.0.0
Nessus Scanner Protocol Error In Security Center
Beta2 and Beta3 When I upgraded from client 2 to 3, i found that my progress bar(s) are
Tenable Security Center Nessus Protocol Error
gone. I loved the fact that client 2 gave you the progress of port scans and vulnerability scans with each client. Now all I can see is that a scan is either on, or done. Not very much help! Are there any plans to put progress bars/status back in? Is there an easy way to count plugins? i found no command line switch in nessusd, nothing in client 3 will tell you how many plugins are installed or even used in a policy. Nessusd 2 (i believe it was 2) would load plugins x/#. I like the progress bar of loading plugins from command line now better, but the only way I can figure to count plugins is out of the Nessus software. Is there a way of counting install plugins other than manually in a browser? Thanks Mike -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- rgula at tenablesecurity Sep7,2007,10:36AM Post #2 of 9 (2151 views) Permalink Re: nessus3 annoyances/wish list [In reply to] Hi Michael, > When I upgraded from client 2 to 3, i found that my progress bar(s) are > gone. I loved the fact that client 2 gave you the progress of port scans > and vulnerability scans with
IP isWhoisCalculatorTool PointsNewsNews tip?ForumsAll ForumsHot TopicsGalleryInfoHardwareAll FAQsSite FAQDSL FAQCable TechAboutcontactabout uscommunityISP FAQAdd ISPISP Ind. ForumsJoin Search similar:congrats to great how-to + establishing Inet connec on VPNYahoo email forced upgrade (again)TekSavvy DSL via Telus blocks inbound ports?Apple announces CarPlay[Mav] QuickBooks for Mac or Parallels...Botnet attack? Forums → Software and Operating Systems → Unix and Linux → Nessus can't listen on port 1241 uniqs3046 Share « disable the ability to remember password to a network share • firefox or something else? » reakyjoin:2004-01-18Killeen, TX reaky Member 2009-Dec-10 1:55 am http://www.gossamer-threads.com/lists/nessus/users/30848 Nessus can't listen on port 1241Hi dearsI have installed nessus 4.2 on RHEL5, It completely installed without any problems and I update It's PlugIns and Activate it and added the Admin user without any problems,The problem is that when I tried to check It's listen ports I found that It just listen to XMLRPC http://www.dslreports.com/forum/r23466566-Nessus-can-t-listen-on-port-1241 port 8834 but not listening to client port 1241, I checked the conf file and found nothing wrong, Listen line is enabled and all things is OK, I can already browse it through web as per there new feature through port 8834 but can't connect to it from out side with nessus client,I checked It's logs too and found that no errors found during startup, Of course I tried too to start and stop it several times and restart all the machine, but still the problem occur ,And of course nothing else useing port 1241, Can anyone help me to find the reason of thatThanks · actions · 2009-Dec-10 1:55 am · SeleniaGentoo ConvertPremium Memberjoin:2006-09-22Fort Smith, AR·Cox HSI Selenia Premium Member 2009-Dec-10 9:25 am I don't use that software but my first guess would be permissions. ports up to 5000 usually require root by default. There are many ways around it. My fav is to keep permissions a
the status of one of the Nessusscanners showed "Plugin Out of Sync". I tried to push the plugins http://rich-notes.blogspot.com/2016/03/manually-update-nessus-plugins.html to the Nessus scanner from the Security Center, but I was getting a status error of "Connection timed out". So basicly I was getting a latency issue on the connection. The Nessus scanner and the Security Center are in different states, so this may be why there is so much latency. I just built this Nessus scanner, protocol error so there were just too many plugins to be pushed over the wire by Security Center. To fix this issue, I just manually copied the plugins to the Nessus scanner. Then I manually loaded the plugins into the Nessus scanner. After I did this, I have not had this issue again. Manually updating the Plugins can sometimes fix scanner protocol error error or scanner status of "Protocol error". These instructions work on Nessus 5x and 6x, when managed by Security Center 4x or 5x. Follow the instructions below to manually install plugins for the Nessus scanner. 1. Login to the Nessus scanner. root@earth> ssh nessus 2. Stop the Nessus service. root@nessus> service nessusd stop 3. Remove the scanner from Security Center. 4. Reset the scanner root@nessus>/opt/nessus/sbin/nessuscli fix --reset Resetting Nessus configuration will permanently erase all your settings and cases Nessus to become unregistered. Do you want to proceed? (y/n) [n]: y Successfully reset Nessus configuration. 5. Connect the Nessus scanner. root@nessus>/opt/nessus/sbin/nessuscli fetch --security-center nessud can now be started, SeccrityCenter will upload the plugins 6. Manually copy over the plugins file. Copy the file tar.gz file from Security Center to or download latest plugins from Tenable. 7. Load the plugins into Nessus. root@nessus>/opt/nessus/sbin/nessuscli update plugins_file.tar.gz * Update successful. The changes will beautomaticallyprocessedby Nessus 8. Start the Nessus service root@nessus> service nessusd start 9. Login to the web interface for Nessus and w
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 21 Oct 2016 01:38:28 GMT by s_wx1062 (squid/3.5.20)