All Apps and Add-ons

SA-ldapsearch 2.0 fails to query global catalog

Splunk Employee
Splunk Employee

Configured LDAP BIND service account to log on to an AD domain controller acting as a global catalog for multiple domains. Queries to the primary domain on the controller work, but queries to any other domain within the global catalog return no results and do not throw an error. Default config is using port 3268 and a null Base DN, with the query itself defining the basedn:

works:

| ldapsearch domain="default" scope=base basedn="dc=primary, dc=domain" search="(objectclass=*)" attrs="*"

fails:

| ldapsearch domain="default" scope=base basedn="dc=other, dc=altdomain" search="(objectclass=*)" attrs="*"

(tried many variations of scope and search strings)

Note that all other AD/LDAP tools in use at the customer site can bind to this same domain controller and browse all the other domains in the global catalog.

0 Karma

Splunk Employee
Splunk Employee

Have you read through the troubleshooting SA-Ldapsearch guid? http://docs.splunk.com/Documentation/SA-LdapSearch/latest/User/UseSA-ldapsearchtotroubleshootproblem...

Maybe specifically :
'Default' stanza
To support context lookups in the "ldapfetch" command, you will also need a "default" stanza that lists a forest-level Global Catalog server by its IP address. In this case, you must specify the port to the Global Catalog. Following is an example:

[default]
server = 172.20.1.2
port = 3268

0 Karma