I have been testing msrpc_dcom.nasl against an NT 4 machine. With a freshly installed 
NT 4 machine without SP6A both nessus and the Eeye scanner do not find it enabled. 
After application of SP6A the Eeye scanner reports it as running DCOM but status is 
unknown. Nessus doesn't report it at all. After application of q823980i.exe from 
Windows Update, the Eeye scanner still reports it as status unknown and Nessus still 
doesn't find it at all.

I've set debug = 1 in the script and rerun it and the output in nessusd.dump in all 
cases says

stud = 00000000

Is there something that can be done with this to get it to report NT 4 systems more 
accurately?


Reply via email to