Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
LDAP Bind was unsuccessful on directory <directory name> for distinguished name '<value>'. Directory returned error:[0x<error code>] <error code>. <Connection Agreement>
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is LDAP?
What is the role of the Microsoft Active Directory Connector (MSADC) ?
In my case, this error occurred because the Exchange SRS service was not running. For some reason it did not start at boot time. I restarted the service and the error went away.
As per Microsoft: "This problem can occur if the target server is down, if it is unreachable due to network problems, or if the Active Directory Connector (ADC) Service Account does not have permissions on the target server". See MSEX2K3DB for additional information about this event.
If the connection agreement has been moved to a E2k or E2k3 server, make sure that the LDAP port is set to 379 (instead of 389) and that the Site Replication Service is started.
See ME288828 and ME821828 for help on troubleshooting this problem.
Lightweight Directory Access Protocol (LDAP) allows you to query and manage directory information using a TCP/IP connection. Check network connectivity. Verify the user name, password, and port address are correct, and try again. If the problem persists, verify that the remote Exchange server is configured to support LDAP.
|Private comment: Subscribers only. See example of private comment|
|Links: ME288828, ME821828, MSADC Events, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated