However, if you have to put a server behind a NAT device and then use an IPsec NAT-T environment, you can enable communication by changing a registry value on the VPN client computer and the VPN server. Therefore, if you must have IPsec for communication, we recommend that you use public IP addresses for all servers that you can connect to from the Internet.
NETGEAR VPN PORT FORWARDING SETUP WINDOWS
This scenario includes VPN servers that are running Windows Server 2008 and Microsoft Windows Server 2003.īecause of the way in which NAT devices translate network traffic, you may experience unexpected results when you put a server behind a NAT device and then use an IPsec NAT-T environment. Therefore, if the virtual private network (VPN) server is behind a NAT device, a Windows Vista-based VPN client computer or a Windows Server 2008-based VPN client computer cannot make a Layer Two Tunneling Protocol (L2TP)/IPsec connection to the VPN server.
NETGEAR VPN PORT FORWARDING SETUP HOW TO
For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:ģ22756 How to back up and restore the registry in Windowsīy default, Windows Vista and the Windows Server 2008 operating system do not support Internet Protocol security (IPsec) network address translation (NAT) Traversal (NAT-T) security associations to servers that are located behind a NAT device. Then, you can restore the registry if a problem occurs. For added protection, back up the registry before you modify it. Therefore, make sure that you follow these steps carefully. However, serious problems might occur if you modify the registry incorrectly. Important This section, method, or task contains steps that tell you how to modify the registry.
0 kommentar(er)
