how to configure windows 2008 server ip routing.docx

8/14/2019 How to configure Windows 2008 Server IP Routing.docx

1/11


2/11

With the removal of OSPF, we are left with either 1) static routing or 2) dynamic routing with

RIPV2. Lets find out how each of these work.

Should you use static or dynamic routing?

The question of whether you should use static or dynamic routing is really a question of

administrative overhead. In the end, the result of your network traffic being routed to the correctnetwork should be the same, no matter what method you choose.

With static routing, you must make an entry on your Windows Server for every networkthatwill be routed by that server. Thus, for a simple network with a single windows server, routingtraffic between two networks, static routing is a no brainer. You could configure it with two

simple route addcommands.

On the other hand, on a network where you want the Windows Server 2008 system to route for25 networks or to exchange routes with a Cisco network that uses RIP, you will want to choose

dynamic routing. Obviously, you do not want to have to key in those 25 networks manually norcan you provide the true dynamic features that RIP provides.

Speaking of that, what does dynamic routing provide you? Lets list out some features.

Ability to automatically add networks by learning them from other RIP routers Ability to automatically remove routes from the routing table when other RIP neighbors

delete them Ability to select the best route based on routing metrics Reduce configuration of Windows Server routing systems that have more than a few

static routes that need to be added

So how do you configure static and dynamic routing in Windows Server 2008?

Static Routing in Windows Server 2008

Static routing in Windows Server is nothing new. We have been using the routecommand for

years. You can configure static routing in Windows 2008 Server using either the route commandor using the GUI. However, if you use the Windows GUI interface, those routes will not be listedin the CLI interface, when you type route print. Thus, I highly recommend that if you are going

to use static routing in Windows 2008, you just use the route command at the windowscommand prompt.

So lets look at some examples of how you configure static routing using the routecommand:

Show the static routing table

Showing the static routing table is easy, just use the route printcommand, as you see in Figure1 below.


3/11

Figure 1: Showing the IP Routing table in Windows Server 2008

In the route print output, the first important thing that you see is the interface list. WindowsServer IP interfaces are labeled with an interface number. The interface numbers in Figure 1 are16, 14, 1, 15, 20, and 12. These interface numbers are used whenever you add or delete routes to

the routing table.

Formatted:Font: (Default) Times Ne12 pt


4/11

The second important thingin the route print output is theIPv4 Routing Table. This shows us

the network destination, network mask, the default gateway, interface, and metric. This table tellsthe Windows Server where to route the traffic.

Below that is the IPv6 routing table. For more information on IPv6, I recommend Brien PoseysarticlesCrash Course in IPv6 (Part One) &Crash Course in IPv6 (Part Two) and Mitch

Tullochs articleIPv6 Support in Microsoft Windows.

Add a static route

So how do you add a static route at the command line? The answer is easy- use the route add

command, like this:

route add 1.1.1.0 mask 255.255.255.0 10.0.1.1 if 1

As you see in Figure 2, the results of our route add was an affirmative OK!

Figure 2: Using the route add command in Windows 2008

What was important in the route add command was the network we want to add, its subnet, thedestination/gateway, and the interface for that route.

Delete a static route

Deleting a route is even easier than adding a route. All you have to do is to tell route deletethenetwork that you want to remove, as you see in Figure 3.

Figure 3: Using the route delete command in Windows 2008

So those are the basics of configuring static routes at the command line. Now lets learn aboutconfiguring dynamic routing.

Dynamic Routing in Windows Server 2008 using RIPV2

Earlier in the article, I talked about the benefits of configuring dynamic routing. So, now let meprovide you the steps to configuring RIPv2 in Windows 2008:

Formatted:Font: (Default) Times Ne12 pt, Bold

http://www.windowsnetworking.com/articles_tutorials/Crash-Course-IPv6-Part1.htmlhttp://www.windowsnetworking.com/articles_tutorials/Crash-Course-IPv6-Part2.htmlhttp://www.windowsnetworking.com/articles_tutorials/IPv6-Support-Microsoft-Windows.htmlhttp://www.windowsnetworking.com/articles_tutorials/IPv6-Support-Microsoft-Windows.htmlhttp://www.windowsnetworking.com/articles_tutorials/IPv6-Support-Microsoft-Windows.htmlhttp://www.windowsnetworking.com/articles_tutorials/Crash-Course-IPv6-Part2.htmlhttp://www.windowsnetworking.com/articles_tutorials/Crash-Course-IPv6-Part1.html


5/11

1. The first step is to install the Routing and Remote Access (RRAS) role in Windows 2008Server. If you go into the Add Roles Wizard, the RRAS role can be difficult to findbecause what you really need to add is the Network Policy and Access Servicesrolethen the Routing and Remote Access Services Role (as you see in Figure 4 and Figure 5).

Figure 4: Adding the RRAS Role through he Network Policy and Access Services



6/11

Figure 5: The Win 2008 Role Services are part of the Network Policy and Access Services Role

Once installed you can configure RRAS from the Server Manager application but I prefer theRouting and Remove Access application.

2. The second part of this is to Configure Routing and Remote Accessby opening theRRAS MMC, right-clicking on the server name, and clicking Configure and Enable

Routing and Remote Access, like this:

Figure 6: Configuring and Enabling RRAS




7/11

Make sure that you do a Custom Configurationconcerning what RRAS protocol to install.

Then, choose to install LAN ROUTING then choose to start the service.

From there, you can see the Network Interfaces controlled by RRAS and specific configurations

for IPV4 and IPV6.

At this point, you can expand IPV4, go to General, then to New Routing Protocol.

Figure 7: Adding a new Routing Protocol

Next, choose to install RIPV2as your routing protocol.



8/11

Figure 8: Adding RIP V2

3. Now that you have RIPv2 installed, you can configure it. Configuring it is really as easyas adding the interfaces that you want to use to exchange RIP routes with. To do this, go

to the RIP section, right click, click on New Interface, select the interface you want toadd under RIP as you see in Figure 9.



9/11

Figure 9: Adding a new RIP interface

4. After selecting the interface, you have the option to configure a wide variety of RIPconnection properties (as you see in Figure 10). There is more to configuring RIP than I

can go into in this article as RIP configuration can either be very simple or it can becomevery complex.



10/11

Figure 10: Configuring the new RIP interface

5. Once you have your RIP interfaces added, you can check to see if you are sending andreceiving responses on your RIP interfaces (you should be). You can also check to see if

you have any RIP neighbors by right-clicking on the RIP protocol, then clicking ShowNeighbors.

Before I conclude this section about RIP in Windows, I want to point you to a couple ofexcellent resources I used while preparing for this article:

1. Recently I was watching Ed LibermansTrain Signal Windows 2008 NetworkInfrastructure video. In that video, besides explaining routing and the differences betweenstatic and dynamic routing, Ed shows, step by step, how to configure RIPv2 in Windows

2008. I found the video very helpful and recommend it to you whether you just want tolearn about Win 2008 and routing or if you are looking to pass Microsofts Windows

2008 Network Infrastructure exam (70-642). Here is a screenshot of Ed configuringRIPV2:

http://www.trainsignal.com/Windows-Server-2008-Network-Infrastructure-Training-P35.aspxhttp://www.trainsignal.com/Windows-Server-2008-Network-Infrastructure-Training-P35.aspxhttp://www.trainsignal.com/Windows-Server-2008-Network-Infrastructure-Training-P35.aspxhttp://www.trainsignal.com/Windows-Server-2008-Network-Infrastructure-Training-P35.aspxhttp://www.trainsignal.com/Windows-Server-2008-Network-Infrastructure-Training-P35.aspx


11/11

Figure 11 Train Signals Windows 2008 Video on how to install and configure RIPV2


how to configure windows 2008 server ip routing.docx

Documents