PPTP-based persistent branch office
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
PPTP-based persistent branch office
The Chicago branch office is a PPTP-based branch office that uses a router running Windows Server 2003, Standard Edition, to create a persistent, router-to-router VPN connection with the corporate office router in New York. The connection is never terminated even when idle.
To deploy a PPTP, two-way initiated, persistent, router-to-router VPN connection to the corporate office based on the settings configured in Common configuration for the VPN server and Persistent Branch Office, the following settings are configured on the corporate router and Chicago router.
VPN server configuration
The VPN server is configured with a demand-dial interface and a static route.
Demand-dial interface for router-to-router VPN connection
To connect the corporate office router to the Chicago router by using a router-to-router VPN connection over the Internet, a demand-dial interface is created by using the Demand-Dial Interface Wizard with the following settings:
Interface name
VPN_Chicago
Connection type
Connect using virtual private networking (VPN) is selected.
VPN type
Point to Point Tunneling Protocol (PPTP) is selected.
Destination address
131.107.0.1
Protocols and security
The Route IP packets on this interface check box is selected.
Static Routes for Remote Networks
Static route for Chicago office network: To make all locations on the Chicago network reachable, the following static route is configured:
Interface: VPN_Chicago
Destination: 192.168.9.0
Network mask: 255.255.255.0
Metric: 1
Dial-out credentials
User name: VPN_CorpHQ
Domain: electronic.microsoft.com
Password: o3\Dn6@`-J4
Confirm password: o3\Dn6@`-J4
Once the demand-dial interface is created, the following change is made:
- For the properties of the demand-dial interface, on the Options tab, under Connection type, the Persistent connection option is selected. To obtain properties of a demand-dial interface, click Routing Interfaces, right-click the desired demand-dial interface, and then click Properties.
Chicago router configuration
The Chicago router is configured with a demand-dial interface and a static route.
Demand-dial interface for router-to-router VPN connection
To connect the Chicago office router to the corporate office router by using a router-to-router VPN connection over the Internet, a demand-dial interface is created by using the Demand-Dial Interface Wizard with the following settings:
Interface name
VPN_CorpHQ
Connection type
Connect using virtual private networking (VPN) is selected.
VPN type
Point to Point Tunneling Protocol (PPTP) is selected.
Destination address
207.209.68.1
Protocols and security
The Route IP packets on this interface check box is selected.
Static Routes for Remote Networks
Static route for the Electronic, Inc. VPN server: To make the Electronic, Inc. VPN server on the Internet reachable, the following static route is configured:
Interface: The WAN adapter attached to the Internet
Destination: 207.209.68.1
Network mask: 255.255.255.255
Gateway: 0.0.0.0
Metric: 1
Static routes for corporate intranet and branch offices: To make all locations on the corporate intranet reachable, the following static route is configured:
Interface: VPN_CorpHQ
Destination: 172.16.0.0
Network mask: 255.240.0.0
Metric: 1
To make all locations on Electronic, Inc. branch offices reachable, the following static route is configured:
Interface: VPN_CorpHQ
Destination: 192.168.0.0
Network mask: 255.255.0.0
Metric: 1
Dial-out credentials
User name: VPN_Chicago
Domain: electronic.microsoft.com
Password: U9!j5dP(%q1
Confirm password: U9!j5dP(%q1
Once the demand-dial interface is created, the following change is made:
- For the properties of the demand-dial interface, on the Options tab, under Connection type, the Persistent connection option is selected.
Notes
Because the WAN adapter creates a point-to-point connection to the ISP, any address can be entered for the gateway. The gateway address of 0.0.0.0 is an example. 0.0.0.0 is the unspecified IP address.
The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred.