Hi, I ran a Nessus scan yesterday on our Novell Servers and two of them crashed. I've run the same scan, service affecting plugins turned off, using Nessus 2 many times without incident. This happened after upgrading to Nessus 3 on RHEL 5.
The servers are running NetWare 6.5 support pack 6, running eDirectory 8.7.3.9 In addition to that, all servers have CIFS modules loaded to provide CIFS access to the filestore. I can't find an overall version number for this, but the CIFS module itself is 3.25, 6th Oct 2006. All servers also have powerpath 3.0.3 and navagent 6.07 installed (this is for communication with the SAN). Each server has eDirectory replicas appropriate to the part of the tree that it generally hosts filestore for (since we clustered things, it's possible for filestore to end up on an inappropriate server, but having the right eDirectory replicas is a mild performance optimisation, not an essential). The first server that crashed did so in CIFS: Engr2 (x.x.x.x, running NWCEngr2 cluster resource, x.x.x.x) abended at 12:48, with a page fault in CIFSPROX.NLM, a module involved in providing CIFS access to filestore. CIFS should be restricted to the clustered address only. The second server that fell over has the ZENWorks PXE services running, and the various modules necessary to support ZENWorks imaging: Sci2 (x.x.x.x, running NWCSCi2 cluster resource, x.x.x.x), abended at 12:54, with a page fault in PMAP.NLM, which is part of the ZENWorks software that provides PXE remote boot capability. I've had a look at the archives and there are some suggestions that NMAP can crash Novell servers, is NMAP used/turned on by default as I can't find any reference to it in the client configuration? Also if NMAP is the problem I don't understand why this never happened with Nessus version 2? Rob Ward Network Northwest Support University of Liverpool Computing Services Department _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
