FYI, The Nmap port scan of high level ports launched from Nessus 1.2.5 seems to crash Veritas Volume Manager on Solaris. This problem manifested itself on multiple Solaris version of 2.6., 2.7, and 2.8 along with Veritas Volume Manager versions of 3.1, 3.1.1, and 3.2. We only captured the port information from two systems. These were the ports that Veritas Volume Manager complained about when the Java GUI was started. 32813 and 32792.
When I removed the high level ports from the Nmap scan the problem stopped. I am just presenting this more for everyone's information, but if someone has a fix I am certainly interested in hearing it! (I know this is not the Nmap list, but as it can be run as a part of nessus...) I was running Nmap with TCP Connect, ID Remote OS, Full Port Range, Do not randomize and normal timing. Thanks! Adrian Mink Security Engineer, Data Security [EMAIL PROTECTED] Work: (602) 371-5302 Pager: (602) 259-2639 "Never mistake for malice what can be explained by incompetence." - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body.
