NetWorker

Last reply by 03-10-2021 Solved
Start a Discussion
2 Bronze
2 Bronze
3595

Create External Authentication Authority: LDAP Error 49

Good morning.

I get the following error when attempting to create a ne External Authority in Network v19:

Creation failed

176230: Unable to add external authentication provider to authentication service. [ErrorMsg: Failed to verify configuration [DOMAIN]: An authentication error has occurred while accessing the naming directory service: [LDAP: error code 49 - 80090308 ldapErr: DSID-0C09044E, comment AcceptSecurityContect errpr, data 52e, v2580], HTTPErrorCode: 400]

I am connecting to a W2K12 DC using LDAP over SSL. I can connect using the same credentials and port using the Windows LDP utility which suggests I may need to tweak a setting in networker.

Regards

 

 

Labels (4)
Solution (1)

Accepted Solutions
4 Beryllium
3592

@petosaur, you have a error code 400 which might mean that the parameters you are passing might be wrong. How are you configuring the integration via the CLI or on the NMC ?

not sure but I think this might help - https://youtu.be/GzB5sqyPTGA.

HTH,
For NetWorker related content - https://www.youtube.com/channel/UC4JLsVyXMyjbQ4i1NaJj5IQ

View solution in original post

Replies (2)
4 Beryllium
3593

@petosaur, you have a error code 400 which might mean that the parameters you are passing might be wrong. How are you configuring the integration via the CLI or on the NMC ?

not sure but I think this might help - https://youtu.be/GzB5sqyPTGA.

HTH,
For NetWorker related content - https://www.youtube.com/channel/UC4JLsVyXMyjbQ4i1NaJj5IQ

3 Argentum
3526

"LDAP: error code 49" and specifically "data 52e" seems to suggest:

codehexdecShort Description More Information
4952e1326ERROR_LOGON_FAILUREReturns when username is valid but password/credential is invalid.

 

https://ldapwiki.com/wiki/Common%20Active%20Directory%20Bind%20Errors

 

Possibly a password with (too) special characters in them? Not with NW but had some issues with Dell DPC appliance hooking it up to AD, as I could not find a way to escape a "!" in the password (at least I recall that being the culprit). Once the password was changed, it worked right away, while before it gave me this very same error.

Latest Solutions
Top Contributor