Note: Since a customer's LDAP system is outside the everything HelpDesk product, the customer is totally responsible to make sure their LDAP system is configured properly. This Knowledge base Article is prepared to help guide you through troubleshooting your LDAP system.
Here are some links for LDAP error codes:
Generic LDAP errors -
http://www.zytrax.com/books/ldap/ch12/#standard
How LDAP Error Codes Map to JNDI Exceptions -
http://java.sun.com/docs/books/tutorial/jndi/ldap/exceptions.html
Novell eDirectory
http://www.novell.com/documentation/nwec/index.html?page=/documentation/nwec/nwec/data/alwxsrr.html#alwxsrr
For active directory:
AD-specific errors appear after the word "data" and before "vece" or "v893" in the actual error string returned to the binding process*
| 525 | user not found |
| 52e | invalid credentials |
| 530 | not permitted to logon at this time |
| 531 | not permitted to logon at this workstation |
| 532 | password expired |
| 533 | account disabled |
| 701 | account expired |
| 773 | user must reset password |
| 775 | user account locked |
*This information provided by the following - http://www-01.ibm.com/support/docview.wss?rs=688&uid=swg21290631
Another option that can help identify the problem is to use Apache Directory Studio (http://directory.apache.org/studio/). This is an LDAP Browser and Directory client that, like everything HelpDesk, is JAVA based. If the Apache Directory Studio gets the same errors that eHD does then there is definitely a problem with your LDAP setup, and your own I.T. support people must correct the problem with your LDAP setup before GroupLink can assist you further on this topic.