Hi, I have just setup a nessus scanner on a Solaris 9 box (this box does not have connectivity to the Internet) and am using an existing nessus 3 client/sever on a Windows 2000 box. The last step I performed in installation of the scanner was to manually update the plugins. Everything seemed to work fine.
To test my installation (especially the plugins), I ran two independent scans, one using the combined Windows client/scanner and another using Windows client with Solaris scanner. Both scans had the same policy and the scans seemed to run fine - until I viewed the results. What is boggling me is my observation that some of the plugins are not being run when I use the second setup i.e. Windows client to setup scan, with Solaris scanner actually doing the scan. I have been careful to restart the nessusd service and also ensure that the plugins are processed. It seems like the plugins folder has been populated with latest plugins, so it doesn't seem to be the case of missing plugins. Has anybody experienced this? Also, I would be interested to know how/what is the interaction between a nessus 3 Windows client and a nessus 3 Solaris scanner i.e. how is the scanner being told to utilize policy x that consists of y checks and where is a log of that stored on the scanner? Does the fact that the Windows version is still in beta, have anything to do with my observation? On a related note, when can we expect to see nessus 3 for Windows generally available, versus in beta? How about timelines aroudn nessus appliances? Thanks in advance for your help! _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
