MX84 Client VPN stopped working with Windows 10

SOLVED
Feral
New here

MX84 Client VPN stopped working with Windows 10

Windows 10 build 1803 changes the VPN client. I am no longer able to connect with any of our Windows 10 laptops to out MX84 client vpn. Has anyone else experienced this issue? 

1 ACCEPTED SOLUTION
Ben
A model citizen

Because you say "When I ping google public dns, the first hop is the provider's switch"

 

Can u try the following?

 

1) Delete the VPN adapter

2) add this rule in the registry 

 

For Windows Vista, 7, 8, 10, and 2008 Server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent 

RegValue: AssumeUDPEncapsulationContextOnSendRule

Type: DWORD

Data Value: 2

 

3) reboot

4) add the vpn connection again and try to connect.

 

 

 

 

View solution in original post

4 REPLIES 4
Ben
A model citizen

Feral,

 

What error message are you getting in the Windows Log on those devices? 

You can find some troubleshooting here for client VPN.

 

https://documentation.meraki.com/MX-Z/Client_VPN/Troubleshooting_Client_VPN

 

Cheers,

Ben

no error. just says:

CoId={DC24308E-9F2B-469E-9C5B-443F193A7EF3}: The user SYSTEM is trying to establish a link to the Remote Access Server for the connection named XXXXXXXX using the following device:
Server address/Phone Number = XXXXXXXXXX
Device = WAN Miniport (L2TP)
Port = VPN3-1
MediaType = VPN.

 

no connection is confirmed. Meraki support confirms they can see my connection, but no traffic.

when I ping google public dns, the first hop is the provider's switch, so I know I am going out the firewall's WAN port, not my home/hot spot. No traffic to the internal side of the firewall.

 

this started after the latest Windows 10 feature update, prior to that the VPN worked fine.

Ben
A model citizen

Because you say "When I ping google public dns, the first hop is the provider's switch"

 

Can u try the following?

 

1) Delete the VPN adapter

2) add this rule in the registry 

 

For Windows Vista, 7, 8, 10, and 2008 Server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent 

RegValue: AssumeUDPEncapsulationContextOnSendRule

Type: DWORD

Data Value: 2

 

3) reboot

4) add the vpn connection again and try to connect.

 

 

 

 

I can now fully connect. it takes a bit but I can ping IPs inside the firewall now. DNS was not fully working yet, but I can work from there. Still have an issue when I connect to the wifi in the building, which is outside of the MX84, but definitely works on my hotspot now, which is a huge improvement. thank you!

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels