I had to check 3 dozens of 3COM SuperStack3 4400 switches in our labs. To avoid unpleasant reconfigurational work, I enabled 'all but dangerous plugins'. I was quite surprised when I saw that Nessus rebooted all the boxes during the scanning process. The network did not run properly after that (the configuration has not been changed by Nessus).
Could anybody tell me, which plugin is in charge for this unpleasant testing behaviour? Thanks in advance. Christoph - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body. * To subscribe again, send a mail to [EMAIL PROTECTED] with "subscribe nessus" in the body
