Configuring the branch office network

Applies To: Windows Server 2008, Windows Server 2008 R2

To configure the dial-up branch office network described in this scenario, the following steps are completed:

1. Installing and configuring the network adapter

2. Installing the Routing and Remote Access service

3. Configuring an IP address pool

4. Installing and configuring dial-up devices

5. Creating demand-dial interfaces

6. Creating dial-in accounts

7. Adding IP static routes

8. Installing DHCP and name servers

9. Testing the branch office network

These steps are outlined in the following sections and are intended as general guidelines for setting up and testing a branch office network.

Installing and configuring the network adapter

To configure Router 5 and Router 6, the following steps are performed:

1. The network adapter is installed.

2. The driver for the network adapter is installed.

3. The IP address on the network adapter is configured through the properties of the TCP/IP protocol.

In this branch office network scenario, the IP addresses are assigned as follows:

• For Router 5, the IP address 172.16.1.3 is assigned to the network adapter that connects to the backbone.

• For Router 6, the IP address 172.16.128.1 is assigned to the network adapter that connects to the branch office network.

Installing the Routing and Remote Access service

For this branch office network scenario, RRAS is installed and LAN and demand-dial routing are enabled. The network adapters that are installed automatically appear as interfaces in RRAS. For more information, see Install and Enable the Routing and Remote Access Service in the RRAS Deployment Guide.

Configuring an IP address pool

In this scenario, the branch office router (Router 6) is configured with an IP address pool with a single range, as shown in the following table.

The corporate router (Router 5) is also configured with an IP address pool with a single range, as shown in the following table.

For information about configuring an IP address pool, see Configure the Routing and Remote Access Service and Demand-Dial Interfaces in the RRAS Deployment Guide.

Installing and configuring dial-up devices

For both Router 5 and Router 6, modem or ISDN devices are installed and configured.

Creating demand-dial interfaces

On Router 6, a demand-dial interface is created by using the Demand-Dial Interface wizard with the following configuration:

• Name: CorpOffice

• Protocols to route: IP

• Modem or adapter: Installed modem or ISDN device

• Phone number: Phone number of Router 5

• Dial-out credentials: BranchOffice

On Router 5, a demand-dial interface is created by using the Demand-Dial Interface wizard with the following configuration:

• Name: BranchOffice

• Protocols to route: IP

• Modem or adapter: Installed modem or ISDN device

• Phone Number: Phone number of Router 6

• Dial-out credentials: CorpOffice

For more information about the Demand-Dial Interface wizard, see Configure the Routing and Remote Access Service and Demand-Dial Interfaces in the RRAS Deployment Guide.

Creating dial-in accounts

For this branch office network scenario, the dial-in accounts are created as follows:

• On Router 6, the account CorpOffice is added and dial-in permissions are enabled.

• On Router 5, the account BranchOffice is added and dial-in permissions are enabled.

For information about creating dial-in accounts, see Configure Router User Accounts in the RRAS Deployment Guide.

Adding IP static routes

For this branch office scenario, on the branch office router (Router 6), a static default route is added. The demand-dial interface that connects to the corporate network is used.

The following route specifies that if a packet is sent to a computer that is not on the branch office network, a demand-dial connection is made with the corporate office. Because the connection between the branch office and the corporate office is a point-to-point connection, the gateway IP address is not configurable.

For more information about configuring a static default route, see Add a Static Route in the RRAS Deployment Guide.

On the corporate router (Router 5), a static route is added in order to connect to the branch office. The following route specifies that all packets destined for the branch office network are sent over the demand-dial interface.

For information about adding static routes, see Add a Static Route in the RRAS Deployment Guide.

The corporate router (Router 5) is configured as an autonomous system boundary router so that the static routes are advertised to other Open Shortest Path First (OSPF) routers.

Installing DHCP and name servers

A DHCP server is installed on the branch office network so that the clients can receive IP addresses without having to send traffic over the demand-dial connection. To access network resources by using names without having to send traffic over the demand-dial connection, a DNS name server is installed.

Testing the branch office network

From a computer in the branch office, run the ping command to ping a computer on the corporate network and activate the demand-dial connection with the corporate network router. After it is connected, run the ping command again. If a reply is received from that computer, the packets are being routed correctly.