Has anyone seen this? I'm running the Nessus 3.2 server on Freebsd 6.3 (upgraded from 3.0.6 and 6.2 freshly), and the 3.2 client on OS X 10.5.2.
I can connect to the remote server with the client fine, and it shows up in both a netstat and a ps -aux on the server without issue. The problem happens when I begin a scan--nessusd churns heavily for about 5 seconds and then drops to 0% CPU usage, and the client either receives no results at all, or just a few things greyed out. I'm running the same set of policies that I was under 3.0.6, and made a few new ones, turning off pingers, trying different portscanners, etc, to see if I could nail down the problem, but to no avail. One interesting point, I did try nessuscmd on the server with the same results---it throws up a few open ports and the number of a hit module or two, but it never exits. Any ideas? Thanks, James _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
