Skip to main content
Could not read AD computers from address
- This issue is typically present when the OC scanner cannot communicate properly with the AD Domain
- controllers in the environment or AD computer object OUs are incorrectly defined in the OC scanner
- Inclusion/Exclusion scope in the OC Configurator > Scan file > Servers > Set OU section.
- To correct the issue make sure ports TCP 88 (Kerberos), TCP 389 (LDAP) are accessible to any OC
- scanners in the network analyzing their respective AD environments.
- Additionally, make sure the user account running the scan has the correct permissions to access the
- given AD Domain Controllers. By default AD Domain Administrators have all the correct permissions to
- access the AD Domain Controllers, as well as AD Domain member servers.
- Check the OC Configurator > Scan file > Servers > Set OU section, and make sure that any OUs defined
- there really exist in the relevant AD tree, and that any OUs are defined with their AD Distinguished name
- attributes, as per the AD Computers and Users console Attribute editor.