06-10-2025 12:38 PM
Hey all!
I'm setting up a new deployment and cannot get the ldap working for a secured wireless network.
I added an AD account to the top of the users OU and set it to the following in the LDAP Admin field;
cn=meraki,dc=Users,dc=intra,dc=domain,dc=gov
When I input the correct username and password for a test, I just hit the following error;
I'm able to ping the internal DC address from the AP with no issues.
Could somebody point me in the right direction for this one?
-Chloe
Solved! Go to Solution.
06-10-2025 01:02 PM
Are you able to do an LDAP bind using those creds from a PC on the same subnet as the APs? You can use the LDP tool to test: https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc771022(v=ws.11)
It's also quite possible there is a Cert issue. You might need to use port 636 instead. Packet captures can really help with diagnosing LDAP connectivity issues. May want to capture the transaction on your server's NIC to verify the traffic is being received and what is happening.
06-10-2025 12:40 PM
06-10-2025 12:56 PM
I've entered it correctly as indicated by the KB, shown in my screenshot above, but the AP keeps failing to connect.
06-10-2025 01:02 PM
Are you able to do an LDAP bind using those creds from a PC on the same subnet as the APs? You can use the LDP tool to test: https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc771022(v=ws.11)
It's also quite possible there is a Cert issue. You might need to use port 636 instead. Packet captures can really help with diagnosing LDAP connectivity issues. May want to capture the transaction on your server's NIC to verify the traffic is being received and what is happening.
06-11-2025 07:53 AM
I placed my laptop on the wireless VLAN and LDP works perfectly with the dedicated meraki account in AD. I'll see if the traffic is passing in Wireshark, but the initial testing with LDP shows a valid and successful connection.
06-11-2025 10:56 AM
After installing Wireshark and watching the traffic, I noticed a SSL/TLS error that lead me to the KB article below. It was the issue outlined in the article that directed me to a cert issue I had to fix.
Active Directory Issue Resolution Guide - Cisco Meraki Documentation
This one is good to go.
@mloraditch you sent me down the right path!
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