|
Lesson 2
Selecting Routers and ISPs
3-21
Practice: Configuring a Windows Server 2003 Router
In this practice, you configure the Routing And Remote Access tool on
Server01 to
route traffic between the two network interface adapters installed in the
computer. For
this exercise, the Microsoft Loopback Adapter is presumed to be connected to
a WAN
device providing a connection to an ISP. The other adapter (which is the
actual net-
work interface card in the computer) is connected to the local private
network. After
configuring RRAS, you then disable it to prepare for later practice.
Note
The Microsoft Loopback Adapter is a software component included with Windows
Server 2003 that you install as part of the server Setup procedure
documented in the “About
This Book” chapter.
Exercise 1: Configuring Routing and Remote Access
In this procedure, you perform a manual configuration that leaves RRAS with
only
basic routing functions.
1. Log on to Server01 as Administrator.
2. Click Start, point to All Programs, point to Administrative Tools, and
then click
Routing And Remote Access. The Routing And Remote Access console appears,
and SERVER01 (local) is listed in the console tree.
3. Click SERVER01 (local), and from the Action menu, select Configure And
Enable
Routing And Remote Access. The Routing And Remote Access Server Setup Wizard
appears.
4. Click Next. The Configuration page appears.
Notice that there are five options that you can select to create different
RRAS
configurations.
5. Select the Custom Configuration. Select Any Combination Of The Features
Avail-
able In Routing And Remote Access option button, and then click Next. The
Cus-
tom Configuration page appears.
6. Select the LAN Routing check box, and then click Next. The Completing The
Rout-
ing And Remote Access Server Setup Wizard page appears.
7. Click Finish. A Routing And Remote Access message box appears, asking if
you
want to start the service.
8. Click Yes. The Routing and Remote Access service starts, and new entries
appear
in the console tree.
Notice that the IP Routing icon contains only three subheadings: General,
Static
Routes, and NAT/Basic Firewall.
|
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)