07-06-2020 01:18 AM - edited 07-06-2020 01:19 AM
Hello,
I have LDAPS issues with my 5515 - asa9-12-3-12-smp-k8.bin
[-2147483602] Session Start
[-2147483602] New request Session, context 0x00007fa9dbdeeb50, reqType = Other
[-2147483602] Fiber started
[-2147483602] Creating LDAP context with uri=ldap://ad.name.local:636
[-2147483602] Connect to LDAP server: ldap://ad.name.local, status = Successful
[-2147483602] Unable to read rootDSE. Can't contact LDAP server.
aaa-server lokal_LDAP (inside) host ad.name.local
server-port 636
ldap-base-dn DC=name, dc=local
ldap-group-base-dn cn=VPN_Berechtigungen, DC=name, dc=local
ldap-scope subtree
ldap-naming-attribute sAMAccountName
ldap-login-password *****
ldap-login-dn cn=ldap,cn=Users, dc=name, dc=local
ldap-over-ssl enable
server-type microsoft
ldap-attribute-map AD_MAP
Cant find why it is not working anymore. No problems with 389 and it also was working with 636 in the past.
Thanks for any proposals.
Best regards, Thorsten
07-06-2020 02:45 AM
- Check if this thread can help you :
https://community.cisco.com/t5/network-security/unable-to-contact-ldap-server/td-p/2628633
M.
07-06-2020 02:58 AM
Thanks for this linked, I´ve checked it already in the morning.
My ldap 389 connect working well - its only a problem if I´m using LDAP over SSL by Port 636.
Thorsten
07-06-2020 03:57 AM
There have been some bugs in the past that had this behavior. For example:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvt46289
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuv32615/?rfs=iqvred
If it's resurfaced on this version, it wouldn't be the first time. I'd suggest opening a TAC case to see if there's a new one that's currently unpublished.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide