Configuring the branch office network
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Configuring the branch office network
To configure the dial-up branch office network described in this scenario, the following steps are completed:
A network adapter is installed and configured.
The Routing and Remote Access service is installed.
An IP address pool is configured.
Remote access devices are installed and configured.
Demand-dial interfaces are created.
Dial-in accounts are created.
IP static routes are added.
A DHCP, WINS, or DNS name server is installed.
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:
The network adapter is installed.
The driver for the network adapter is installed.
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, the Routing and Remote Access service is installed and LAN and demand-dial routing are enabled. For more information, see Enable the Routing and Remote Access service. The network adapters that are installed automatically appear as interfaces in Routing and Remote Access.
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.
| Starting address of the range | Ending address of the range | Number of addresses in the range |
|---|---|---|
172.16.128.253 |
172.16.128.254 |
2 |
The corporate router (Router 5) is also configured with an IP address pool with a single range, as shown in the following table.
| Starting address of the range | Ending address of the range | Number of addresses in the range |
|---|---|---|
172.16.1.133 |
172.16.1.134 |
2 |
For information about configuring an IP address pool, see Create a static IP address pool.
Installing and configuring dial-up devices
For both Router 5 and Router 6, modem or ISDN devices are installed and configured. For more information, see Installing Dial-Up Equipment.
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 Add a demand-dial interface.
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 dial-in user properties.
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.
| Interface | Destination | Network mask | Metric |
|---|---|---|---|
CorpOffice |
0.0.0.0 |
0.0.0.0 |
2 |
For more information about configuring a static default route, see Add a default static IP route.
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.
| Interface | Destination | Network mask | Metric |
|---|---|---|---|
BranchOffice |
172.16.128.0 |
255.255.255.0 |
2 |
For information about adding static routes, see Add a static route.
The corporate router (Router 5) is configured as an autonomous system boundary router so that the static routes are advertised to other OSPF routers.
Installing a DHCP, WINS, or DNS name server
A DHCP server is installed on the branch office network so that the clients can receive IP addresses. For more information about DHCP, see DHCP Overview. To access network resources by using NetBIOS or domain names, a WINS or DNS name server is installed. For more information, see WINS Overview and DNS Overview.
Notes
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.
Open Shortest Path First (OSPF) is not available on Windows XP 64-bit Edition (Itanium) and the 64-bit versions of the Windows Server 2003 family.