MX 17.10.2 - can't connect via Client VPN

[nbit]

I have two uplinks. When I switched to the new one, VPN stopped connecting. I now switched back to Wan1 and it still won't connect.

Where do I find any inf/log for this or how do I troubleshoot this?

Thank you.

[PhilipDAth]

Are you using the Microsoft L2TP client or Cisco AnyConnect?

Are you connecting to the dynamic DNS name on the MX or a hard coded WAN IP?

Does the MX have a public IP on each WAN circuit directly configured on the MX, or is one/both uplinks plugged into something NATing to a private IP on the MX WAN interface?

[nbit]

Two separate ISPs plugged into WAN1 and WAN2. IPs. The first one had a name and everyone connected to that for years.

And no AnyConnect, just regular Mac OS VPN.

[alemabrahao]

Have you tested It wirh another OS?

[Frank-NL]

Hi,

You can find logging in the event log, filter on "Non-Meraki / CLient VPN" events.

Switching between uplinks with the client VPN is tricky, especially when it's a short period of time. Like Philip is saying it depends on the way you are trying to connect.

[nbit]

Nothing in the log for yesterday. 

I tried connecting now and it stayed connected. Weird.

[Frank-NL]

Definitely something with the MX, we’ve had difficulties as well with failovers but usually it’s up and running quite fast. Do you think its something in the 17 version?

[alemabrahao]

If It's a Windows machine you can take a look on Windows event viewer. 

https://documentation.meraki.com/MX/Client_VPN/Guided_Client_VPN_Troubleshooting#Common_Windows_erro....

[nbit]

The next morning I tested and it worked, again. Thank you, all for the responses.