{"id":70,"date":"2016-08-01T14:46:58","date_gmt":"2016-08-01T14:46:58","guid":{"rendered":"http:\/\/172.23.1.43\/?p=70"},"modified":"2022-06-07T22:26:30","modified_gmt":"2022-06-07T22:26:30","slug":"vpn-l2tp-error-809","status":"publish","type":"post","link":"https:\/\/blog.n-dol.org\/2016\/08\/01\/vpn-l2tp-error-809\/","title":{"rendered":"VPN \u2013 L2TP Error 809"},"content":{"rendered":"
If you’re using L2TP with IPSec.<\/p>\n
Windows doesn’t activate NAT-T by default (Windows 10 included) you need to add a registry key:<\/p>\n
To create and configure the<\/p>\n
AssumeUDPEncapsulationContextOnSendRule registry value, follow these steps:<\/p>\n HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\PolicyAgent<\/strong><\/li>\n
\n<\/em><\/p>\n\n
\n
\nA value of 0 (zero) configures Windows so that it cannot establish security associations with servers that are located behind NAT devices. This is the default value.<\/li>\n
\nA value of 1 configures Windows so that it can establish security associations with servers that are located behind NAT devices.<\/li>\n
\nA value of 2 configures Windows so that it can establish security associations when both the server and the Windows Vista-based or Windows Server 2008-based VPN client computer are behind NAT devices.<\/li>\n<\/ul>\n<\/li>\n