Configuring a Cisco router to exchange RIP routes with a Windows 2003 Server - Part 2
Did you know that a Windows Server can act as a router? Even better, did you know that a Windows server could be configured to exchange routes with a Cisco router? In Part 1 of this series, we demonstrated how to configure a Windows 2003 Server to exchange routes with a Cisco router using RIP. In this second part of the series, we will configure the Cisco router and prove that these configurations work. Let’s get started!
If you’ll remember from Part 1 of this series, we offered a diagram of our sample network. To refresh your memory, here is what it looks like.
Passwords Haven’t Disappeared Yet
123456. Qwerty. Iloveyou. No, these are not exercises for people who are brand new to typing. Shockingly, they are among the most common passwords that end users choose in 2021. Research has found that the average business user must manually type out, or copy/paste, the credentials to 154 websites per month. We repeatedly got one question that surprised us: “Why would I ever trust a third party with control of my network?
Configure a Cisco Router to exchange routes with a Windows 2003 Server
I have configured my Cisco router with interfaces in the two networks shown above. Here is the relevant configuration:
interface Ethernet0/0 ip address 10.253.15.38 255.255.0.0 ! interface Loopback0 ip address 220.127.116.11 255.0.0.0
To configure the Cisco router to advertise these RIP routes and exchange then with the Windows Server, I enable RIP version 2 and add these networks to the RIP routing process:
Router#conf t Enter configuration commands, one per line. End with CNTL/Z. Router(config)# router rip Router(config-router)# ver 2 Router(config-router)# network 10.253.0.0 Router(config-router)# network 18.104.22.168 Router(config-router)#exit Router(config)#exit Router#
What we did was this:
- Enter RIP configuration mode on the router
- Configure RIP to use version 2 so that subnet masks will be sent with routing updates, allowing us to use classless IP routing, with out network conflicts in the routing protocol
- Add the two networks to RIP using the network ID for each network – this tells RIP to both ADVERTISE this network to RIP neighbors and to LOOK FOR RIP neighbors on these networks.
RIP Route exchange between Windows 2003 Server and the Cisco IOS
Now, for the moment of truth, did it really work? To find out, on the router, just issue the show ip route command. What you should see is a route coded as a R route, for RIP. If your Cisco router has a route received as a RIP route (marked R), then you know that your router received that route from a neighbor. The only neighbor we have configured is the Windows 2003 Server RIP router. It should look something like this:
As you can see, our Cisco router received RIP route 192.168.182.0 from 10.253.15.163 – our Windows 2003 Server.
To prove that we have communication, I pinged the Local Area Connection 2 interface on the far side of the Windows 2003 Server, from where the router is – 192.168.182.128. This proved that there was complete communication through the Windows 2003 Server, in one side and out the other side.
Now, let’s look at the stats over on the Windows 2003 server.
Notice how the Windows server has been receiving RIP updated on one of the interfaces – those updates are coming from the Cisco router. To see the RIP route for the 22.214.171.124 network over on the Windows 2003 Server, at the command line, we do route print, like this:
Notice the 126.96.36.199 route being received from the 10.253.15.38 gateway.
And, we can ping 188.8.131.52 from the Windows Server, like this:
In conclusion, we have successfully configured a Cisco router to exchange RIP routes with a Windows 2003 Server. Overall, I I hope that you found that it was much easier than you thought. The route exchange and interoperability between these two different platforms is made possible by the RIP standards. By being able to use a Windows Server as a router or exchanging routes between various routers or firewalls and a Windows Server, you are opening yourself up to so many options for your network design and configuration.
Recent Cisco Forum threads
Got a question? Post it on our Cisco Forum!