AD/Network scan

Hello,

I am testing SDP and have found that additionally to the many problems reported about the asset scanning of clients in AD i have encountered this issue, which i havent found reported by any others yet.

The scan is using FQDN to identify the client and fails with DCOM or access denied.
If i manually scan and use the netbios name only the scan is successfull.

I have noticed a problem with our AD, because we use a 3rd party DNS and our network numbers 1000's with many subnets so in some cases the DNS name registered in AD is not the same as that fron the DNS (AD takes the top level domain name and the dns is using a subnet associated dns name).

However I still get the above behaviour of success using netbios; failure of network or AD scan even after correcting the DNS entry in AD using ADSIedit.

To be clear there is no firewall inbetween our VLANS so therefore no ports are being blocked and some machines are ok and others not regardless of VLAN with no other obviouse reason for the failure.

I dont really want to manually add 500+ machines

Hope this helps in troubleshooting some others problems that may be similar.

Thanks

Stevo