Windows 10: L2TP VPN Stopped Working After Windows 10 1803 07_2018 Update

Hello,


I have been using the built-in Windows 10 VPN client to connect to both a Cisco and a Ubiquiti Edgerouter using L2TP/IPSec with a pre-shared secret. After multiple PCs loaded the 07_2018 Windows 1803 update, all of the VPN connections failed to connect. One of my coworkers found an article which contained the following registry hack:


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PolicyAgent]

Add “AssumeUDPEncapsulationContextOnSendRule”=dword:00000002


Reboot.


Apparently this 'tells' the client to 'tell' the VPN server that the client is behind a NAT device. Why this was not necessary before escapes me. It used to work without it to both devices, so it's a Windows change that broke it.


Anyway, this registry change fixed two of my computers but the third still refuses to connect. The cause appears to be that the L2TP layer doesn't come up on the failing machine. I have tried disabling the Windows firewall, logging in as a different user in case it was the profile, and deleting and re-adding the VPN connection. Nothing seems to work. There is one difference with this machine, it is new and was updated to 1803 BEFORE I added the VPN connection. The others had loaded 1803 months ago and were loading the monthly updates to 1803. Not sure why this would make a difference, but that is the case with the one machine which still refuses to connect even after the registry hack is applied.


Thanks in Advance....


Zeldar

:)

 

L2TP VPN Stopped Working After Windows 10 1803 07_2018 Update

Hello,

I have been using the built-in Windows 10 VPN client to connect to both a Cisco and a Ubiquiti Edgerouter using L2TP/IPSec with a pre-shared secret. After multiple PCs loaded the 07_2018 Windows 1803 update, all of the VPN connections failed to connect.
One of my coworkers found an article which contained the following registry hack:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PolicyAgent]

Add “AssumeUDPEncapsulationContextOnSendRule”=dword:00000002

Reboot.

Apparently this 'tells' the client to 'tell' the VPN server that the client is behind a NAT device. Why this was not necessary before escapes me. It used to work without it to both devices, so it's a Windows change that broke it.

Anyway, this registry change fixed two of my computers but the third still refuses to connect. The cause appears to be that the L2TP layer doesn't come up on the failing machine. I have tried disabling the Windows firewall, logging in as a different user
in case it was the profile, and deleting and re-adding the VPN connection. Nothing seems to work. There is one difference with this machine, it is new and was updated to 1803 BEFORE I added the VPN connection. The others had loaded 1803 months ago and were
loading the monthly updates to 1803. Not sure why this would make a difference, but that is the case with the one machine which still refuses to connect even after the registry hack is applied.

Thanks in Advance....

 

L2TP VPN on Lumia 950 giving error code 812

Hello,

I recently purchased a Lumia 950 (AT&T running Windows 10 Mobile build 10.0.10586.0.

When I configure my work IPSec L2TP VPN connection on my phone and then attempt to connect, it attempts to connect, then fails displaying the error:

The VPN connection failed with error code 812.

This seems to happen after the credentials are accepted.

During the connection attempt on the phone, the status display progresses as follows:

• Connecting to <address of my VPN server>
• Verifying your credentials
• Connecting to <address of my VPN server>
• The VPN connection failed with error code 812.

When I look at the logs of my VPN server, a connection is actually established successfully by the client, then immediately terminated.

I'm not positive who is terminating the connection on who (client or server).

VPN Settings configured on the Lumia 950 are as follows:

Connection name: My Work

Server name or address: <address of my VPN server>

VPN Type: L2TP/IPsec with pre-shared key

Pre-shared key: <pre-shared key that is configured on my VPN server & working on other devices>

Type of sign-in info: User name and password

I have typed the username & password in again multiple times to confirm it is correct. It is.

Furthermore, I have a Lumia 925 running Windows Phone 8.1. It connects perfectly using these same settings.

It seems something changed in Windows 10 Mobile that caused this VPN connection to stop working.

Do you have any suggestions on how I might be able to get this resolved?

I really need the VPN to be working.

Thanks!

-

Doug Mortensen

Impala Networks

 

VPN L2TP server

I have previously configured a Windows 10 pc to accept incoming VPN traffic via broadband using PPTP protocol, but now that Apple have discontinued PPTP support on IOS/OSX based devices in favour of other protocols e.g. L2TP/IPsec, I have no apparent
way of accessing my private network via an Apple client and a Windows based VPN server. Is there is a way to do something similar via an Apple based client and a Windows 10 pc running an L2TP based server?