Routing Information Protocol (RIP) is a routing protocol that allows routers to communicate with each other.
In this tutorial, we will set up 2 RIPv2 servers to allow the machines of 2 local networks to communicate with each other (if the firewalls allow it).
With RIP, clients of a local area network will be able to communicate with clients of the other local area network without the need to add static routes to the different clients of those local area networks.
To set up the RIP protocol on a server, you need 2 network adapters :
Note that the third network adapter is not required for RIP. However, for the example to be complete, we have chosen to add a third network card to allow servers and client devices to access the Internet via NAT.
Note : if you want to configure the NAT as well (as explained later in the tutorial), we recommend that you add the 3 network adapters before you configure the "Routing and Remote Access" service. Otherwise, you will have to remove the configuration from this service and recreate it after a server restart.
For this tutorial, we used 2 servers running Windows Server 2012 R2 and 2 client machines running Windows 8.1 Pro (one per LAN).
As mentioned previously, our 2 servers have 3 network cards each :
Configuring the "RIP interface" network card :
Note : leave the other fields blank, as they will not be used for this network interface.
Configuring the "LAN" network card :
Note : leave other fields blank.
Configuring the "WAN" network adapter :
For DNS configuration, specify :
As mentioned previously, we used 2 servers under Window Server 2012 R2 Standard.
These two servers are named "rip1" and "rip2".
Note : the edition doesn't matter.
For client machines, we used 2 computers under Windows 8.1 Pro, with this network configuration :
To install the RIP protocol, you must install the "Remote Access" role on both servers.
To do this, launch the Add Roles and Features wizard and choose "Role-based or feature-based Installation".
Choose your server and click Next.
Check the "Remote Access" box.
No feature to install.
Check the "Routing" box.
Note : this role service depends on the "DirectAccess and VPN (RAS)" role service. So the "DirectAccess and VPN (RAS)" box will be automatically checked.
The installation is done.
Note : don't forget to do the same on your 2nd server.
To configure routing in Windows Server 2012 R2, open the Windows Home screen, click the small arrow at the bottom left, then launch the "Routing and Remote Access" program.
The "Routing and Remote Access" window appears.
Right-click the name of your server and click "Configure and Enable Routing and Remote Access".
The Routing and Remote Access Server Setup Wizard appears.
Select "Custom configuration".
Check the "LAN routing" box.
Click Start service.
To configure your server to act as a RIP server, go to IPv4 and right-click "New Routing Protocol" on the "General" item.
Choose the "RIP Version 2 for Internet Protocol" routing protocol and click OK.
Now go to "IPv4 -> RIP" and right click "New interface" in the right part.
Select the network interface that allows you to interconnect your RIP servers.
For the option "Added cost for routes", enter this value : 2.
Otherwise, the packets may not reach their destination because they will expire too soon.
Now, your RIP server will share the routes it knows via the "RIP Interface" network card.
Windows Server 4/28/2012
Windows Server 4/22/2015
Windows Server 12/9/2016
Windows Server 12/3/2016
® InformatiWeb-Pro.net - InformatiWeb.net 2008-2022 - © Lionel Eppe - All rights reserved.
Total or partial reproduction of this site is prohibited and constitutes an infringement punishable by articles L.335-2 and following of the intellectual property Code.