Trying to conect Windows 10 to L2TP VPN, connection "... failed because security policy for the connection was not found

Trying to conect Windows 10 to L2TP VPN, connection "... failed because security policy for the connection was not found

Client behind NAT devices
Solution: Modern Windows devices do not support L2TP/IPsec connections when the Windows computer or VPN server are located behind a NAT. 
If the Windows VPN client fails with Error 809 when trying to establish a VPN connection to an MX located behind a NAT, add the
"AssumeUDPEncapsulationContextOnSendRule" DWORD value to the Windows registry. This DWORD value allows Windows to establish security 
associations when both the VPN server and the Windows based VPN client computer are behind NAT devices.
 

For Windows XP:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IPSec

RegValue: AssumeUDPEncapsulationContextOnSendRule

Type: DWORD

Data Value: 2
 

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

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent 

RegValue: AssumeUDPEncapsulationContextOnSendRule

Type: DWORD

Data Value: 2
 

Note that after creating this key you will need to reboot the machine. For more information, reference the Microsoft Support Knowledge Base.

    • Related Articles

    • Deferring Windows updates through Group Policy

      Run gpedit.msc Navigate to Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update -> Windows Update for Business Open "Select when Preview Builds and Feature Updates are received". Set it according to the picture ...
    • Setting Default Programs in Windows (mail & web browser)

      Setting the correct Default Programs on your windows pc will ensure best compatibility with your day to day activities in the workplace. Some services and websites will ONLY work on specific browsers and Encompass specifically needs to have Outlook ...
    • secman64.dll specified module could not be found

      Pasted from Ellie Mae's knowledge base, article number 000011391. ---- You will need to re-register the secman.dll and secman64.dll files to clear this message:  Open an elevated command prompt window: Start >type in "cmd" > right-click on the ...
    • FHA Connection Registration

      1.       Go to FHA Connection Welcome page 2.       Click “Registering and New User” (shown below) 3.       Click the third bullet point: Standard User Registration form 4.       Enter the following required fields: name, phone number, mother’s ...
    • Windows Search/Outlook doesn't index properly

      Go to C:\ProgramData\ Right-click on the Search folder Select Properties Select the Security tab Click "Advanced" Click "Change permissions" (this requires a UAC prompt) Check the "Replace all child permission entities..." box at the bottom of the ...