@amacaya    I see that one of the VPN clients was connected on Aug 5 at 13:22:45. If you are still having an issue, I would recommend troubleshooting the issue with support. I see that case is supported pending, NSE will reach back to you soon.   Meanwhile, you can provide a packet capture in Wireshark taken on the MX when the device is trying to connect along with the username from which the connection was being attempted. Also, provide the error core you are seeing on the end device.   I would also recommend testing a VPN connection from another machine such as Mobile/MacOS.    Make sure, the configurations on the machine is not changed and it is the same as per the document: https://documentation.meraki.com/MX/Client_VPN/Client_VPN_OS_Configuration   - Sanket      ... View more

@DetroitJeremy @DavidHenley @JRMcGee    I totally understand the Major issue we had before. We are still working on RCA for the issue and waiting for update from the Engineering team.   Once that verbiage is created, we’ll update all of the cases attached to the issue so our customers get an update regarding RCA. Please look for an email on the cases you have created.   Once again I sincerely thank you for patiently waiting for the issue to be fixed.    Regards, Sanket Kosrabe Cisco Meraki Support  ... View more

Hello Everyone,   Just to keep you all informed on the config fetch outage/Client VPN, a fix has been deployed to all shards, nodes will now be able to fetch their configurations if a Dashboard change is initiated or so out of date nodes should self-correct as they fetch configs according to their backoff timers.   We thank you for your patience and support on this.  ... View more