We're working on getting LDAP authentication to function with a Windows 2003 DC; however, authentication is failing. (using LDAP browser, getting error 49
Details:
CN=kbox,CN=users,DC=Nightingale,DC=local

Steps completed:
* Used admin uname/pw; used known working LDAP uname/pw
* verified uname/pw work (standard Windows logon)
* used more than one DC, by name, by FQDN, and by IP
* verified port (we are using LDAP with other services as well)
* used password with no special characters
* tried OU=Users rather than CN=Users
* tried without CN/OU=Users

Any ideas on what could be incorrect?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Tim,

I have a guide that I wrote for LDAP on the KBOX. Take a look at it and make sure that you are following the instructions in it.

You can download it at dtxdropbox.dell.com

Login Name: ldap
Password: elpcegpp

Also if you could post you search filter and base DN as well that would help us figure out where it might be going wrong. Also for your authentication user make sure that you use either the domain\username format or use the distinguishedname of the user (looks something link this. (CN=admin,CN=users,DC=domain,DC=com)

Brandon
Answered 08/18/2011 by: WhitzEnd
Seventh Degree Black Belt

Please log in to comment
0
Hi Brandon,
I was trying to configure K1000 Virtual appliance for LDAP Authentication to login to the web interface with AD users.
username and password you provided do not work. Could you update the information?
Thanks.
Answered 11/25/2011 by: Darzogij
Yellow Belt

Please log in to comment
1
Here is a sample screen shot of a functioning LDAP K1000 console login configuration. Hope it helps!


Answered 11/25/2011 by: scottlutz
Orange Senior Belt

  • This screenshot helped me greatly.
Please log in to comment
Answer this question or Comment on this question for clarity