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

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)" <[email protected]>
> 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
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus