Meraki Client VPN, Connection Terminated By Remote Computer

VPN
1

Hi All, I am trying to connect a Windows 10 pc back to an MX64 via the VPN Client. After trying to connect to it I receive, “This connection was terminated by the remote computer before it could be completed.” I have followed the Meraki documentation to set up the VPN client on my windows 10 machine. I have the correct hostname, the correct pre-shared secret key, and my Meraki auth is correct as well. I have a two-factor setup for my user, and at first, I thought that was the issue, but I tried it again with the user who doesn’t have two-factor on, and we still get the error. I have removed the VPN connection in Windows twice, IPV6 disabled, PAP, and mschapv2 enabled. I cannot find out where I am going wrong here I have seen this issue multiple times. I have check firewall rules and service startup as well.

​

Any ideas would be greatly appreciated!

2

The dial in VPN is very fussy in Windows 10 with Meraki

If you do not follow the instructions here (link below) EXACTLY then you get all sorts of errors

Eg you say you’ve got mschap2 switched on. And the instructions say not to.

Remove VPN and follow exactly. Even down to using the dynamic name for the external address rather than the IP

Don’t second guess it or think that any deviation won’t matter, it will

Ask me how I know this…or rather…ask me how I know this NOW…

3

When I have that happen it’s usually that Microsoft Chap is checked and unencrypted is unchecked. Make sure your Data Encryption setting is correct as well. I often times will just walk through the setup steps again as it’s typically pretty fast to do so. Good luck!

4

This fixes mine 99.9%. Windows10 vpn client is flakey 1. Remove the window vpn. 2 Go-to device manager. Uninstall mini port adapter wan ip and mini wan lL2tp. 4.Then goto action at the top and scan for hardware changes. 5. Reconfigure vpn. 6 Try reconnecting msg me if you have any questions. I recently migrated our company to meraki vpn from anyconnect.

5

Take a look to the event viewer, you may find out some code errors useful for troubleshooting.
The last chance (or first if you like it) is using Draytec vpn client that avoids all errors and fix registry for missing sets

6

Lots of good advice here - I have been using this powershell script to create my win10 vpn entries and it fixes 95% of problem connections (the others being user firewall or IPv6 related):
https://github.com/gammacapricorni/happy-meraki-client-vpn

7

This is what I’ve found to fix my VPN issues multiple time, when I have checked and rechecked that the settings are correct.

​

Go into Device Manager> Network Adapters

Right click and Uninstall all WAN Miniport Adapters individually.

When done, click on Action>Scan for hardware changes, and all the WAN Miniports will reinstall.

Try the VPN again, and it should work properly.

8

Wanted to jump in and say I’ve got the same issue with our Windows clients. macOS works just fine, Windows stopped working earlier this year even on machines where it was working fine for the last three years. I’ve configured the client VPN enough over the years where I have it memorized.

Tried everything everyone’s listed here including a powershell script I found in another forum and made sure to add the registry entry. Tried on two different machines. Even created a fresh win10 VM on my mac and it won’t connect either. Tried different networks and hotspot from my phone. Did a packet capture on the MX WAN interface and when reviewing in wireshark it looks like ISAKMP Phase 2 is looping on Next Payload (5). I’ve got a support ticket open with Meraki. Willing to share anything that might help if they figure it out.

9

I’ve found IPv6 is the usual culprit in my environment, so I gotta agree with this, check that first.

10

There documentation is very helpful, however I notice sometimes I do everything right and when I try and connect it a end user it still fails - most the time the user is working off their home network. Not sure if it is something with their router or ISP or what - they don’t get along though.

Any ideas?

​

Also, how long does it take for a change made in the Meraki dashboard to rollout to the end user? You sound like you have some experience with this problem.

11

Assuming good internet to the MX, then changes are made on the device within minutes.

Every time I try and remember what the steps are, I miss a small detail and it doesn’t work.

Following the instructions to the letter does work for me.

It might also be oddness with the end users device.

Testing with a vanilla and fresh w10 build might show that. No AV, no left over previous VPN software drivers etc

I’d also check that the dial in VPN subnet that the MX as assigns doesn’t conflict with the users home IP range.

Also need to check that end user is not behind double NAT or CGNAT…ie do they have an actual, publicly addressable ipv4 address. Can you get to the remote admin page on their router (temporarily) if you browse to whatever they see in ipchicken.com?

Then if still not working, I’d raise a Meraki support case f they’ll be able to get to the bottom of it.

Or DM me and I’ll be happy to try and help (UK time)