With LDP, you can perform operations such as connect, bind, search, modify, add, delete against any Lightweight Directory Access Protocol (LDAP)-compatible directory, such as Active Directory Domain Services (AD DS). LDP is an LDAP client that you use to view objects that are stored in AD DS along with their metadata, such as security descriptors and replication metadata. Kindly refer to the following related guides: “The application /Certsrv does not exist: How to configure Certificate Enrollment Web Services and Certificate Authority Web Enrollment“, How to import a certificate into the Trusted Root and Personal file certificate store, how to import a certificate into the Trusted Root and Personal file certificate store, how to request a certificate signing request in Windows using Microsoft Management Console, and how to export a certificate in PFX format in Windows.
This error is as a result of no SSL certificate implemented already to bound to the LDP to connect successfully to the domain controller. When this is implemented correctly, you will be able to connect to the domain controller with an SSL connection. For guides on resolving some windows issues please check these: How to fix the issue “The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license” and how to fix the issue “The Security Database on the Server does not have a Computer Account for this Workstation Trust Relationship” on Windows Server [Part 2], and how to quickly Fix Windows Search Bar Not Working.
If the SSL is not implemented yet then you will get the below result. In the next steps, I will be referring you to a solution that will help resolve this issue.
In order to resolve this issue, kindly refer to this guide If you are using a self-signed certificate, you will need to set up Active Directory Certificate Services via the server manager server roles. For a comprehensive guide on how to fix this issue completely, kindly refer to this guide “How to generate a self-signed SSL certificate bound to an IP address“.
After installing the certificate, when next you try to bound the SSL with the IP address on the Ldp page as shown below, the error will no longer be present.
This is because there is an SSL certificate implemented already in the LDP and this will enable a successful connection to the domain controller. Now test the Ldp connection again and you should be able to connect now as shown below.
If this does not resolve your issues, please take a look at the Windows Event Logg to get more details about the error reason. Launch the Windows Event Viewer and navigate to the following session.
Event Viewer - System Log
I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.