When I try to add an LDAP server of type Active Directory, I get the following error message:
"Query returned no domain controller records. Verify that the server has at least one domain controller and the user has required permissions."
I have a sneaking suspicion this issue relates to bullet #1 below. Unfortunately, I cannot change this as security requires the ePO server not be joined to the domain.
There are a couple threads with this same error message and no resolutions. That doesn't bode well, but even if I knew why it didn't work, that would be helpful in determining if this is the right product/solution for our requirements:
Any insight would be greatly appreciated.
Does it work if you uncheck use ssl? Is the domain controller using ldap channel binding? Refer to KB92298. Does the orion log show any connection failures? Does the domain controller show any connection failures in event logs?
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
I don't see any errors in the DC logs. My DCs require SSL. Unchecking the box gives a different error stating SSL is required.
There are tons of logs for ePO. I did find something something relevant in the orion.log file when I try to create the LDAP registered server:
WARN [http-nio-8007-exec-22] internal.LdapConnectionImpl - Unable to retrieve any records using query '(servicePrincipalName=*)'.
WARN [http-nio-8007-exec-22] ldap.LdapAction - com.mcaffeorion.ldap.ldapqueryexception: Query returned no domain controllers records. Verify that the server has at least one domain controller and the user had required permissions.
I receive this error each time I click the "Test Connection" button.
I searched the ePO forums for servicePrincipalName and got no relevant hits.
See if you can test with ldp.exe.
This has instructions (disregard that it is cisco)
and this is where you can get it from
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Sorry for the delay ...
Yes, I'm able to connect, bind and query the domain/forest using LDP.exe without issue. For Base DN I used DC=<domain>, DC=<com>, for Filter I used (objectClass=*), Scope was set to One Level, and Attributes was set to *.
It returned all data.
What version of epo are you running and any updates installed?
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
I'm running v5.9.1 (Build 251)
What do you get when you go through this?
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
If I do it from a domain-joined system, it returns my three domain controllers.
If I do if from the non-domain-joined ePO server, it returns non-existent domain. I'm really beginning to think it has to do with the ePO server being a non-domain joined system (workgroup).
I have seen it work, but you may need to possibly put host file in for domain controller. Not on the domain, there might not be dns resolution, even if you do have the dc in dns settings. Does nslookup resolve the domain name? If not, then try a host file for domain name as well as fqdn of domain controller.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA