Merkai Vpn Not Working Update Their Client

How does the Anti-Cheat services from gaming interfere with IPsec.

L2TPIPSec with PSK.

Domain authentication with Windows Server AD.

Nothing in the configuration on the firewall or the server has changed.

We are a small company with under 30 users, we tend not to change anything if we dont have to.

Clients use built-in windows client, both myself and the user were working with existing client side configurations within the last month.

I can ping the gateway from two separate computers (two independent networks outside of the VPN network, mine and his).

However, when you try and connect the vpn it goes to Connecting and then hangs.

I have removed the VPN configuration on the client side and reconfigured each from scratch, and also confirmed that the user credentials are working for both users on the domain.

The event log on the domain controller is showing no issues with failed connections, but I dont look enough to know exactly what Im looking for.

What are some steps I should take to troubleshoot next Here is the event log from Meraki.

Sep 11 17:15:52 e0:cb:bc:05:b7:cd Non-Meraki Client VPN negotiation msg: invalid DH group 20.

Sep 11 17:15:52 e0:cb:bc:05:b7:cd Non-Meraki Client VPN negotiation msg: received broken Microsoft ID: MS NT5 ISAKMPOAKLEY Edit: I changed authentication back to Meraki Cloud, continues to hang on Connecting.

Also tried to change the VPN authentication host address to the default one that you get from Meraki, neither have worked.

Which sucks. From a reasonably secure IPv4 public address to our client VPN address, it works perfectly.

The problem comes that, when thrust into the real world, it fails in a wide variety of scenarios.

So after banging my head against the wall for three weeks, something that shouldve been well documented on their end ultimately made their Client VPN useless.

Merkai Vpn Not Working Update Their Client

I made a suggestion to update their Client VPN for something a bit more modern (or at least adding IPv6 support through the entire MX series and its feature sets, such as VPN and firewall), but thats all I can do.

TL;DR: it works in a perfect test world, but doesnt work out in the real world of 2017.

Disappointing, but thats what a Windows Server is for, I suppose.

What threw me off was that a coworker was experiencing it and I wasnt aware he was a gamer.

I had this happen a while ago and it only started after I installed a few games (after just getting my computer).

My guess is that anti-cheat services cause issues with ipsec.

If I restart the ipsec protocol in services, it will work again, if I reboot, it works again.

Very strange issue, but I know what is happening now.

Thank you.

Merkai Vpn Not Working For Mac