LDAP Administrator 2008.x or 3.x
When you connect to the Active Directory server using LDAP Administrator 2008 or 3.x expanding a first level node cases Operations Error with message The operation being requested was not performed because the user has not been authenticated or Invalid Credentials with The logon attempt failed.
LDAP Browser 2.x
When you connect to the Active Directory server using LDAP Browser 2.x, in the Output window or the messages.log file you'll see the following lines:
- Code: Select all
Successfully connected to adserver.company.tld
Schema cache does not exist or expired. Fetching new one...
AttributeTypes: Total: 0 Invalid: 0 Duplicated: 0
LDAPObjectClasses: Total: 0 Invalid: 0 Duplicated: 0
MatchingRules: Total: 0 Invalid: 0 Duplicated: 0
You may experience such a behaviour when you connect to the Active Directory server anonymously or use invalid credentials. Windows logon name notion if often confused with the notion of LDAP DN. The former one could not be used to Active Directory authentication.
Unless specially configured, it is imperative you provide valid credentials for connecting to the Active Directory server.
To edit your credentials, open Server Profile Properties. Choose the Credentials tab and enter the proper user name and password into the corresponding input boxes. Generally, the Active Directory credentials have the following format: CN=Windows_User_Name,CN=Users,DC=company_name,DC=domain. For example: CN=John Smith,CN=Users,DC=example,DC=com. It's also possible to use the Kerberos principal name. For example: firstname.lastname@example.org.
If you use LDAP Administrator 3.3 or later you may opt for using Currently logged on user checkbox and do not type any credentials information at all.