According to MS, it's likely a driver issue -- have you seen their KB article on the topic?
 
http://support.microsoft.com/kb/256004
 
I'd consider the registry work indicated to see if you can find any more information on which driver may be at fault, if this is indeed the issue.
 
Mike


[EMAIL PROTECTED] wrote: -----

To: <[email protected]>
From: "Ron Korszoloski" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
Date: 10/07/2007 08:43AM
Subject: Nessus 3.0.6.1 Crashes Windows Small Business Server 2003 Premium

Unfortunately this is the only box with enough capability to install Nessus on at this customers’ site.  This is a fresh install of Nessus with the default configuration. I tried to scan 192.168.60.0/24 and 192.168.60.100-192.168.60.200, both time the server crashed with a BSOD.

Stop: 0x0000003F (0x00000000, 0x00000002, 0x00000002, 0x000057FF)

 

Hardware is:

Dell PowerEdge 2600

Dual 2.8 GB Xeon CPUs

2 GB Memory

 

Operating System is Windows Small Business Server 2003 SP2 with all the latest patches.

 

I’m new to Nessus and am afraid to continue trying this product on this server. Needless to say a Microsoft Small Business server is loaded with software to begin with, IIS, MSSQL, Exchange, ISA etc. It’s a one server solution. It appears Nessus should be installed on it’s own machine, but this network consist of old hardware, Pentium 600s with 384MB of ram and Windows 2000.

 

Any Suggestions?

 

TIA,

RK

 

_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to