Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About VincentM
Community Record
9
Posts
1
Kudos
1
Solution
Badges
Aug 5 2021
1:24 PM
I'm going to go out on a limb and say your issue is probably due to the much greater Meraki Cloud Certificate issue that everyone else is going through today. The issue specifically effects VPN tunnels. I went on to the community to see if there were any updates and came across your post so I figured I weight in.
... View more
Jul 2 2020
10:25 AM
1 Kudo
It turns out that the new router was not configured properly. I should have know better than to think that the Meraki was to blame.
... View more
Jun 28 2020
6:58 AM
I’ve confirmed that the DNS record updates with the new circuit virtual IP. It appears now that the issue is with the new router; UDP ports 500 & 4500 may not be open to allow any 3rd party VPN tunnels and client VPN tunnels. Waiting on the ISP to confirm.
... View more
Jun 26 2020
10:26 AM
Thanks again for looking into this. I spoke to Meraki today and the DNS server that the MX uses is an AWS leased by Cisco in San Fransisco. They gave me a procedure to follow to update the WAN 1 info allow an update to the DNS. I will be testing this over the weekend or on Monday evening and I will report back.
... View more
Jun 24 2020
3:51 PM
I also want to point out that authentication for clients is done through the Meraki Cloud, not AD.
... View more
Jun 24 2020
3:48 PM
I searched my DNS records and there is no entry for the Meraki VPN - the only entry for this device is the name of the firewall with the LAN Gateway address.
... View more
Jun 24 2020
2:02 PM
Yes, which is why I've configured all of our clients to connect to the host name as opposed to the IP address so when there is a fail-over to WAN 2 or we update our circuit IP info, they will (in theory) still be able to connect. Unfortunately for me, this wasn't the case.
... View more
Jun 24 2020
8:46 AM
They are set to got to a name. What type of change to the connection setup do you think is required?
... View more
Jun 24 2020
8:29 AM
We are upgrading our internet circuit and router; the ISP provided new IP information; WAN 1 IP information was edited with new IP info; and Virtual IP info was updated with new IP since we have a warm spare configuration. Internet access was available, however, client VPN did not complete any connections. I was forced to revert back to the old circuit. Any ideas as to why VPN clients were unable to connect to the MX?
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 3351 | Jul 2 2020 10:25 AM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 1 | 3351 |
© 2024 Cisco Systems, Inc.
