Question
3356 views

L2TP registry change to work with NAT-T not working on Windows 10

perikles asked on

I have been using this solution on my Win 8.1 

https://support.microsoft.com/en-us/kb/926179

After updating to Windows 10 it is not working any more.

Is there a work around for it?

21 people had this question

Abuse history


The answered status icon Answer
DanielJNielsen replied on

I've managed to make my two windows 10 (64bit pro) installations connect to l2tp behind nat, using the mentioned registry key with value 2. 

I went into regedit, changed the key to 1, rebooted, changed the key back to 2, rebooted and now I can use VPN via l2tp again.

Regards, Daniel 

8 people found this helpful

Abuse history


JonFC replied on

I can confirm that the issue is present in Windows 10 Pro (64 bit) too.

Like @perikles, I was able to connect to an L2TP/IPSec VPN applying the mentioned solution in Windows 8.1 or Windows 7, but not anymore with the new OS. Until the problem is fixed we won't be able to upgrade all the computers in our office.

Be the first person to mark this helpful

Abuse history


The answered status icon Answer
DanielJNielsen replied on

I've managed to make my two windows 10 (64bit pro) installations connect to l2tp behind nat, using the mentioned registry key with value 2. 

I went into regedit, changed the key to 1, rebooted, changed the key back to 2, rebooted and now I can use VPN via l2tp again.

Regards, Daniel 

8 people found this helpful

Abuse history


perikles replied on

Yes worked for me too (Win 10 Home) 

Thank you

1 person found this helpful

Abuse history


robiscool replied on

I had this problem with synology NAS vpn server with windows 10. I have been advised the following from their support:

"Many thanks for your recent support request regarding Synology NAS and the issue you have encountered. I can confirm that this is most likely related to a service not running on the Windows device correctly.
Please can you ensure that the "IKE and AuthIP IPsec Keying Modules" and "IPsec Policy Agent" services are either started or set to start automatically as these are required."

When I checked the services I found that 'IPsec Policy Agent' wasn't running or set to turn on. I'm yet to test this outside my network but thought I'd post the possible solution before I forget later. Good luck!

RW

pc enthusiast
1 person found this helpful

Abuse history