John Ballance
asked on
LDP "bind with credentials" failing
LDAP connection failing with below error, I have successfully tested the credentials , I can telnet on 389 and 636 although I am testing over 389 when I get this error:
Error <49>: ldap_bind_s() failed: Invalid Credentials.
Server error: 8009030C: LdapErr: DSID-0C09056D, comment: AcceptSecurityContext error, data 52e, v2580
Error 0x8009030C The logon attempt failed
Anybody experienced this issue before?
Error <49>: ldap_bind_s() failed: Invalid Credentials.
Server error: 8009030C: LdapErr: DSID-0C09056D, comment: AcceptSecurityContext error, data 52e, v2580
Error 0x8009030C The logon attempt failed
Anybody experienced this issue before?
ASKER
Thanks Myousufali but the error described in this article is related to simple bind failing
If you are certain that the credentials are accurate, then you are probably specifying the user logon name in an incorrect format.
The error code 49 related to LDAP is caused by the invalid credentials.
Please refer to the following most possible causes.
1. The DN path or password which you have specified for the administrator is invalid. Any of the below will result in this error:
a). Pointed to non-user DN
b). Pointed to a non-existent user, but in existing DN
c). Pointed to non existent DN
d). Pointed to an existing user, but non existing DN
e). Pointed to an incorrect admin DN, uid instead of cn
f). Pointed to a non administrator user
g). Pointed to a valid admin but password is incorrect
2. Could not authenticate the user trying to login. This can be the result of an incorrect username or password,
or an incorrect prefix and/or suffix specified in the Settings tab, depending on the type of LDAP/AD system.
Could also mean the authentication type is incorrect.
Please refer to the following most possible causes.
1. The DN path or password which you have specified for the administrator is invalid. Any of the below will result in this error:
a). Pointed to non-user DN
b). Pointed to a non-existent user, but in existing DN
c). Pointed to non existent DN
d). Pointed to an existing user, but non existing DN
e). Pointed to an incorrect admin DN, uid instead of cn
f). Pointed to a non administrator user
g). Pointed to a valid admin but password is incorrect
2. Could not authenticate the user trying to login. This can be the result of an incorrect username or password,
or an incorrect prefix and/or suffix specified in the Settings tab, depending on the type of LDAP/AD system.
Could also mean the authentication type is incorrect.
@myousufali - you copied that straight off a Microsoft forums site without giving attribution. Which is: https://social.technet.microsoft.com/Forums/office/en-US/c98f3569-072a-4677-9b89-635ed2b8dffc/ldap-error-code-49-8009030c-ldaperr-dsid0c0903a9-comment-acceptsecuritycontext-error-data
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Check this article by Clint Bossen's. Hope this will solve your problem.
http://clintboessen.blogspot.com/2011/06/error-49-ldapsimplebinds-failed-invalid.html
Thanks.