On Fri, Nov 07, 2008 at 08:59:25AM -0800, Ray Van Dolson wrote: > On Fri, Nov 07, 2008 at 08:44:18AM -0800, Paul Davis wrote: > > Ray, > > > > What steps other than disabling the firewall and enabling remote > > desktop were taken on this system? There's a blog entry for scanning > > Windows Vista systems for FDCC Compliance which details steps to > > enable policy compliance scanning on systems with Security Center > > such as Vista (or 2008). > > > > I am currently successfully scanning a Windows 2008 system for audit > > compliance, and IIRC, I configured it using the steps in this blog > > entry: > > > > http://blog.tenablesecurity.com/2008/02/testing-windows.html > > > > Paul > > Paul, I believe I found the issue. My initial hypothesis that I had > something misconfigured on the Windows 2008 side was incorrect... I > took a peek at the Nessus scanner logs and saw the following: > > Couldn't load /opt/nessus//lib/nessus/plugins/nessus_tcp_scanner.nes > - libssl.so.4: cannot open shared object file: No such file or > directory > > This is using the Fedora 8 RPM of Nessus. However, Fedora 8 only has a > libssl.so.6 file. :) Probably some libraries within Nessus need to be > relinkned against the proper .so... > > However, easy workaround was to create a symlink from libssl.so.4 (and, > as it turns out, libcrypto.so.4) to the corresponding .so.6 files. > > Re-ran the scan and everything seems to be working now. > > Sorry for the wild goose chase! >
Actually, one additional step was required on my part to get the Windows 2008 scan to work completely correctly. I had to disable UAC for local accounts (done via the registry). Support pointed me to this blog link which contained the relevant instructions: http://blog.tenablesecurity.com/2008/02/testing-windows.html Everything is working as-expected now. Thanks! Ray _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
