I'm seeing this as well, on a Nessus VM I've been using (and regularly
updating) successfully for the past 6 months. Updated my plugins today
and scan.exe is crashing.
Date: Wed, 30 Jan 2008 11:08:21 -0500
From: "Jason Bertoch" <jason@electronet.net>
Subject: scan.exe crash
To: <nessus@list.nessus.org>
Message-ID: <079001c8635a$56174070$6338a8c0@electronet.net>
Content-Type: text/plain; charset="US-ASCII"
Hi all,
Yesterday, I installed Nessus on a WinXP machine and
successfully
scanned a server from outside my firewall. This morning I installed
another
copy on an internal Xen virtual XP machine to scan from a different
point of
view. Each time I tried to scan, scan.exe would crash with following
attempts
giving the error "Can not connect to Nessus Server!". I then moved the
install
to a virtual 2003 server and had the same results.
I considered that there may have been a plugin update since my
install
yesterday so I updated the external XP machine which worked fine
yesterday.
After the plugin update, it is now doing the same thing as my internal
machines.
Could the current update contain a corrupt plugin? Is anyone else
seeing this?
Jason A. Bertoch
Network Administrator
jason@electronet.net
Electronet Broadband Communications
3411 Capital Medical Blvd.
Tallahassee, FL 32308
(V) 850.222.0229 (F) 850.222.8771
------------------------------
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
End of Nessus Digest, Vol 51, Issue 27
**************************************
Andrew Brannan, CISSP
USDA OCIO/ITS/IDB/IOLab
Infrastructure Deployment Branch - IO Lab
5601 Sunnyside Avenue
Rm 2-1174B
Beltsville, Maryland 20705-5740
301-504-4173
Date: Wed, 30 Jan 2008 11:08:21 -0500
From: "Jason Bertoch" <jason@electronet.net>
Subject: scan.exe crash
To: <nessus@list.nessus.org>
Message-ID: <079001c8635a$56174070$6338a8c0@electronet.net>
Content-Type: text/plain; charset="US-ASCII"
Hi all,
Yesterday, I installed Nessus on a WinXP machine and
successfully
scanned a server from outside my firewall. This morning I installed
another
copy on an internal Xen virtual XP machine to scan from a different
point of
view. Each time I tried to scan, scan.exe would crash with following
attempts
giving the error "Can not connect to Nessus Server!". I then moved the
install
to a virtual 2003 server and had the same results.
I considered that there may have been a plugin update since my
install
yesterday so I updated the external XP machine which worked fine
yesterday.
After the plugin update, it is now doing the same thing as my internal
machines.
Could the current update contain a corrupt plugin? Is anyone else
seeing this?
Jason A. Bertoch
Network Administrator
jason@electronet.net
Electronet Broadband Communications
3411 Capital Medical Blvd.
Tallahassee, FL 32308
(V) 850.222.0229 (F) 850.222.8771
------------------------------
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
End of Nessus Digest, Vol 51, Issue 27
**************************************
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
