Win10 L2TP/IPsec

Set-Service -Name "RemoteAccess" -StartupType Automatic

Start-Service "RemoteAccess"

dir "HKLM:\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Rasman"

Get-ItemProperty "HKLM:\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Rasman\Parameters"

New-ItemProperty -Path "HKLM:\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\Parameters" -Name ProhibitIPSec -Value "0" -PropertyType "DWord" -Force

New-ItemProperty -Path "HKLM:\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent" -Name AssumeUDPEncapsulationContextOnSendRule -Value "2" -PropertyType "DWord" -Force

New-ItemProperty -Path "HKLM:\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Rasman\Parameters" -Name AllowL2TPWeakCrypto -Value "1" -PropertyType "DWord" -force

 

https://docs.microsoft.com/en-us/previous-versions//cc939765(v=technet.10)

0	Routing and Remote Access conducts IPSec negotiation on L2TP calls.
1	Routing and Remote Access does not conduct IPSec negotiation on L2TP calls.

 

此键值说明如下：

https://docs.microsoft.com/en-us/previous-versions/bb878119(v%3dtechnet.10)

• 0 = SAs cannot be established with servers that are located behind NATs (default)
• 1 = SAs can be established with servers that are located behind NATs, provided the client has a public address
• 2 = SAs can be established when both client and servers are located behind NATs (this is the behavior for Windows XP with Service Pack 1 and Windows XP with no service packs installed)

重启计算机。