Renaud, I am running a scan against a remote Win2K machine (I'm in Australia, it's in Singapore, so I'm not completely sure of its configuration). The scan "dies" at about 65% consistently, immediately after executing cgitest.nasl. (I set it to execute only one plugin at a time to be sure).
Cgitest completes, but from that point on nothing happens. Sniffing packets shows nothing going out or in from Nessus. Nessus is still alive (I can terminate the scan) and its CPU usage is unusually high. From nessusd.messages: [Wed Jan 22 17:08:47 2003][31395] user mw : launching cgitest.nasl against xx.xx.xx.xx [31848] . . . a swag of "Not Launching" messages here . . . [Wed Jan 22 17:08:54 2003][31395] cgitest.nasl (process 31848) finished its job in 7.454 seconds [Wed Jan 22 22:19:10 2003][30514] user mw : stopping attack against xx.xx.xx.xx [Wed Jan 22 22:19:10 2003][30514] user mw : stopping attack against xx.xx.xx.xx [Wed Jan 22 22:19:10 2003][30514] *** utils.c:466 trying to remove 'xx.xx.xx.xx' from 0x0 [Wed Jan 22 22:19:10 2003][30514] user mw : test complete [Wed Jan 22 22:19:10 2003][30514] user mw : Kept alive connection [Wed Jan 22 22:19:11 2003][30514] Communication closed by client There seems to no further clue as to what is stopping it. Any ideas where to look? -Matt
