After updating (uninstall old, clean install new) from Nessus 2.6 to 3.0.3, our recent scan caused multiple abends on our NetWare 6.5 servers. It effected about 50% of the servers scanned.
Abend was: EIP in LIBC.NLM at code start +0008BB95h Running process: BTCPCOM.NLM 6 Process Thread Owned by NLM: BTCPCOM.NLM Safe checks were enabled and port scanning was enabled. This approach worked ok with (no NetWare abends) using our previous version of Nessus. I did read a Novell TID from 2003 (2966492) concerning a field fix for Nessus port scanning causing an abend with Btcpcom.nlm, but all our servers have the same date and version recommended by the TID. Servers are a mix of NetWare service pack level, SP2, SP3, SP5. We are working to get all to SP5. It was about a 50-50 mix of effected servers in relation to the service pack level. I have yet to find any pattern to pursue, other than the obvious info from the abend logs. Does anyone have similar experience or any insight? Thanks Joel Elwell Network Security Engineer Corporate Email Administrator [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
