Issue with Anywhere Connect AD Authentication (Meraki)

[Curits]

Hey Guys,

Looking for some advice for something, we have just installed a new Meraki device at a customers, this is my first time using one of these. I have gone to enable Anywhere Connect for user VPN access. I have got it working when using Meraki Cloud Authentication but we are wanting to use the local active directory. I have entered the domain name, IP of server and then username and password of the domain admin. It doesn't seem to have any issues with it but when I go to authenticate myself on the client also as an admin (tried a separate admin account and the one entered into Meraki) it just doesn't authenticate. Is there something further I need to do here?

Thanks for the help in advance.

[alemabrahao]

There are some step configurations in AD that you must follow:

https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/Configuring_Active_Direc...

[PhilipDAth]

For this to work the AD controller must have a certificate installed (self signed is fine) as the MX uses LDAPs.  One of the easier ways to do this is to install just the IIS Manager (you don't need IIS itself installed), click on certificates, and then click on create self-signed certificate.

[Rick-G]

Hey Curits!

The previous advice about using the documentation to retrace your steps is great advice. An additional resource to help troubleshoot once you confirm proper configuration can be found here:

https://documentation.meraki.com/MX/Client_VPN/AnyConnect_on_the_MX_Appliance/AnyConnect_Troubleshoo...

It outlines several scenarios where authentication can fail and provides steps for remediation. Please give that a shot and if you continue to have issues, please let us know!