Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Re: Unable to scan with Nessus when hosts have FDCC implemented

Subject: Re: Unable to scan with Nessus when hosts have FDCC implemented
Date: Wed, 30 Jul 2008 13:43:56 +0000
to get  nessus to work under FDCC  I believe you have to open tcp port 135 and 
allow remote access to the registry

--John
--
"When the legend becomes fact, print the legend." 


 -------------- Original message ----------------------
From: "Puerto, Richard (IG/A/ITSA)" <RPuerto@usaid.gov>
Hello All,

We have come across a site the we were auditing and conducting network
vulnerability scans, and the Nessus report came up empty. We figured out
that it was due to having FDCC implemented and the Nesssus scanner was
unable to access the machine. It would detect the host being there but
not able to access any of the host's ports.

Any one else encounter this and has found a solution?

 




--- Begin Message ---
Subject: Unable to scan with Nessus when hosts have FDCC implemented
Date: Wed, 30 Jul 2008 13:39:54 +0000
Hello All,

We have come across a site the we were auditing and conducting network
vulnerability scans, and the Nessus report came up empty. We figured out
that it was due to having FDCC implemented and the Nesssus scanner was
unable to access the machine. It would detect the host being there but
not able to access any of the host's ports.

Any one else encounter this and has found a solution?

 

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

--- End Message ---
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
<Prev in Thread] Current Thread [Next in Thread>