Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
New user of Meraki MX75 ASA here. We had Cisco Secure Client VPNs set up on our ASA 5516 that the MX75 replaced which required getting an SSL cert from a CA for our subdomain, webvpn.domain.org, applying that SSL cert to our ASA, and adding an A rec...
We opted for the profile option using the linked profile editor for creation of the .xml file.It worked like this:Created a profile with a different name than our already-used webvpn.domain.org, went to Client VPN settings in dashboard and Enabled 'P...
Can you verify this is the process & walk through what goes in the blanks on the profile editor? This sounds easy.1. Use profile editor link given earlier and download and save a profile file:*VPN name #1: assuming webvpn.domain.org ??*Hostname/Outs...
To be honest, that's what I currently have in place (thinking that would work), but obviously, Meraki picks up on that somehow and returns a certificate error to users that it's not a secure connection. Right now, they are having to click through a ...
Sorry for the late reply. I've been further investigating pros and cons and am still unsure.1. I realize that using the DDNS name is easiest. However, we only have a handful of users already connecting using the Secure client on company issued lap...
Thanks for the reply. In order for this to work, will I need to put the public IP in the CSR request as a SubjectAltName? I watched a YouTube video that showed that's how they did it. I really would like this to work on the first attempt. Or, doe...