Export (0) Print
Expand All

RIP-for-IP Routed Network Example

Updated: April 30, 2010

Applies To: Windows Server 2008, Windows Server 2008 R2

This topic describes a medium-size office network using RIP-for IP configured as shown in the following illustration.

Medium-size office network

In the previous illustration, routers 1, 2, and 3 are computers running RRAS that serve as IP routers connecting the backbone network to other subnets that make up the organizational network. Router 4 is a dial-in RRAS server that hosts a set of modems that support dial-up client computers.

The following sections describe how IP addresses are assigned for this medium-size office network scenario.

Network IDs are assigned based on the private network ID of 192.168.0.0 for each network segment that uses a subnet mask of 255.255.255.0. This provides for growth of up to 254 computers on each network segment.

The following table shows the assignment of IP addresses for this scenario.

IP addresses for the medium-size office network

 

Segment IP network ID with mask Range of host IDs

Backbone

192.168.1.0, 255.255.255.0

192.168.1.1 - 192.168.1.224 (excludes addresses reserved for dial-in clients on network D – see last row in table)

Network A

192.168.2.0, 255.255.255.0

192.168.2.1 - 192.168.2.254

Network B

192.168.3.0, 255.255.255.0

192.168.3.1 - 192.168.3.254

Network C

192.168.4.0, 255.255.255.0

192.168.4.1 - 192.168.4.254

Network D

Static range for dial-in clients (reserved in DHCP so they can’t be reused)

192.168.1.225 - 192.168.1.254

After planning the network for this medium-size office, addresses are assigned (either manually or by using DHCP) in the ranges described in the preceding table for all other computers on Networks A, B, C, and D.

The IP routing protocol for medium-size networks is Routing Information Protocol (RIP) version 2. In this scenario, RIP v2 is configured on RRAS Routers 1, 2, 3, and 4.

For this scenario, the DHCP service is used to automatically configure IP addresses and other information on client computers. Because DHCP is used, the DHCP Relay Agent must be configured on RRAS Routers 1, 2, and 3. When the DHCP Relay Agent is used, client computers on Networks A, B, and C can acquire addresses from the DHCP server on the backbone network. Router 4 can supply dial-up clients with IP addresses either by using DHCP (effectively serving as a DHCP routing agent), or by using a static pool of addresses.

noteNote
You do not need to use the DHCP Relay Agent on a router if you have a DHCP server on each network segment.

To configure the medium-size office network described in this scenario, the following steps are completed:

  1. Installing and configuring network adapters

  2. Installing the Routing and Remote Access service

  3. Configuring RIP

  4. Configuring remote access devices

  5. Installing and configuring the DHCP Relay Agent

  6. Installing a DNS name server

These steps are outlined in the following sections and are intended as general guidelines for setting up and testing a medium-size office routed IP network.

To install and configure network adapters, the following steps are performed:

  1. Two network adapters are installed in every router.

  2. The drivers are installed for the network adapters.

  3. The TCP/IP protocol is installed.

  4. IP addresses are configured on the network adapters.

The following table shows the IP addresses assigned to network adapters in this medium-size office network scenario.

 

Router and connection IP address

Router 1 to Backbone

192.168.1.1

Router 1 to Network A

192.168.2.1

Router 2 to Backbone

192.168.1.2

Router 2 to Network B

192.168.3.1

Router 3 to Backbone

192.168.1.3

Router 3 to Network C

192.168.4.1

Router 4 to Backbone

192.168.1.4

For this medium-size office network scenario, RRAS is installed and enabled as a LAN router on every router. For more information about installing the Routing and Remote Access service, see Install and Enable the Routing and Remote Access Service in the RRAS Deployment Guide.

On Router 4, RRAS is installed and enabled as a LAN router and as a remote access server. An IP address pool is created with a starting address of 192.168.1.225 and an ending IP address of 192.168.1.254. This pool allows up to 29 simultaneously connected dial-up networking clients. IP addresses for interfaces on the backbone network must now be selected so that they are within the range 192.168.1.1 to 192.168.1.224. The DHCP scope that serves the backbone network must exclude those addresses to prevent them from being reused.

For more information about creating IP address pools, see Configure the Routing and Remote Access Service and Demand-Dial Interfaces in the RRAS Deployment Guide.

On each router, the RIP protocol is configured. To configure RIP, the RIP routing protocol is added to IP, each interface is added to RIP, and then RIP version 2 is enabled on the RIP interface that is connected to the backbone. For more information, see Configure RIP Version 2 in the RRAS Deployment Guide.

This scenario assumes that all the routers on the medium-size office network are servers running RRAS that are configured for RIP version 2. If there are existing routers on the network that only support RIP version 1, then you must install and configure RIP version 1.

In this routing scenario, Router 4 is a remote access server for dial-up networking clients. On Router 4, remote access devices such as modems and ISDN adapters are installed.

To use DHCP on the network, the DHCP Relay Agent is installed on Routers 1, 2, and 3. The interfaces that are not on the backbone are configured to use the DHCP Relay Agent, and the DHCP server is configured for use by clients.

For information about configuring the DHCP Relay Agent, see Configure the DHCP Relay Agent in the RRAS Deployment Guide.

To access network resources by using DNS name, a DNS name server is installed.

For this scenario, the ability of the medium-size office network to route packets is tested by answering the following questions:

  1. Are the packets being routed correctly?

  2. From a computer on each network, run the ping command to ping a computer on each of the other networks. If a reply is not received from a network, the packets are not being routed correctly. Are the RIP packets being sent correctly?

    To ensure that RIP packets are sent correctly, view the neighboring RIP routers from one RIP router. Neighboring RIP routers are routers connected to a common network. For information about viewing RIP neighbors, see View RIP Neighbors in the RRAS Deployment Guide.

  3. Are all the networks being routed to?

    To ensure that all the networks are being routed to, view the IP routing table from a router. For more information, see View Routing Tables in the RRAS Deployment Guide.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft