|Title||LDAP: Active Directory connection try to discover the nearest DC now|
|Check_MK Edition||Check_MK Raw Edition (CRE)|
|Level||1 - Trivial Change|
|Compatibility||Compatible - no manual interaction needed|
The LDAP connection of the Check_MK GUI is now using the configured LDAP
server to detect the nearest Domain Controller of the current domain. Speaking
to the nearest domain controller will increase the performance of the LDAP sync.
The discovery is done like this:
A connection is established with the configured server. Normally this is the
DNS name of the AD domain. For this connection a "random DC" is used. In fact
the given name is locally resolved using DNS and one answered IP is picked.
The authentication with the default credentials is done.
The AD site of the local system is detected.
This is done by gathering the local IP subnets and searching the AD sites for
The first DC of the found AD site is used instead of "server".
In case the detection does not work the "server" that has been handed over to this
function is used.
When you experience errors with this enable debug logging for LDAP
(Global Settings > User Interface > Logging > LDAP) and check out
the var/log/web.log for details.
To the list of all Werks