SSTP is a new kind of Virtual Private Networking (VPN) tunnel that is available in the Routing and Remote Access Server role in Windows Server 2008. SSTP allows for Point-to-Point Protocol (PPP) packets to be encapsulated over HTTP. This allows for a VPN connection to be more easily established through a firewall or through a Network Address Translation (NAT) device. Also, this allows for a VPN connection to be established through an HTTP proxy device.
The information is this article is more likely to apply to a small-sized or medium-sized organization. For these kinds of organizations, it is common to have one public IP address that is assigned to the external interface of a NAT router or of a gateway device. This article describes the following scenario:
- You have a Windows Server 2008-based Secure Socket Tunneling Protocol (SSTP)-based VPN server.
- The server is assigned a private IP address.
- The server is located on an internal network behind a NAT device.
OverviewThe information in this article relates to the following networking configuration example:
- A NAT device has the following IP address assignments:
- The following public routable IP address is assigned to the external interface: 184.108.40.206
- The following private non-routable IP address is assigned to the internal interface: 192.168.0.1
- On a DNS server that can be accessed externally, the public IP address 220.127.116.11 is mapped to the following fully qualified domain name (FQDN): vpn-1.contoso.com.
- A Windows Server 2008-based Routing and Remote Access server has the following IP address assignments:
- IP address: 192.168.0.2
- Subnet mask: 255.255.255.0
- Default gateway: 192.168.0.1
Configuration informationWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To configure a SSTP-based VPN server in the scenario that is described in the "Overview" section, follow these steps:
- Configure the NAT device to redirect SSTP traffic from the external network to the Windows Server 2008-based computer that will act as the SSTP-based VPN server. Specifically, redirect incoming traffic as follows:
- Source IP address: 18.104.22.168 (the external interface)
- Source port: TCP 443
- Destination IP address: 192.168.0.2 (the IP address of the Routing and Remote Access server)
- Destination port: TCP 443
- Install a computer certificate on the Windows Server 2008-based computer. This certificate must have a subject name (CN) that is the same as the host name to which the VPN clients connect. This is required for SSL negotiation to succeed.
- If a VPN client is configured to connect to the public IP address of the NAT device (22.214.171.124), the subject name of the certificate must be 126.96.36.199.
- If a VPN client is configured to connect to the FQDN (vpn-1.contoso.com) that can be accessed publicly, the subject name of the certificate must be vpn-1.contoso.com.
- Use the Server Manager tool to install the Network Policy and Access Services role together with the Routing and Remote Access Services role service on the Windows Server 2008-based computer.
- After the Routing and Remote Access Services role service is installed, configure the Routing and Remote Access service by using the Routing and Remote Access Services Wizard.
- If you want to configure the SSTP-based VPN server to listen on a port other than TCP port 443, follow these steps:
- Start Registry Editor, and then locate the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SstpSvc\Parameters\
- In the details pane, right-click ListenerPort, and then click Modify.
- Click Decimal, type an alternative port number such as 5000, and then click OK.
- Exit Registry Editor, and then restart the Routing and Remote Access service.
- Start Registry Editor, and then locate the following registry subkey:
Article ID: 947032 - Last Review: Mar 6, 2008 - Revision: 1