route add

ipconfig /setclassid

MCSA 70-642

IP networks, including home networks, enterprise intranets, and the Internet, consist of a series of interconnected routers. Routers forward traffic to computers, to other routers, and finally to a destination computer. At the most basic, client computers send all communications through a single router known as the default gateway. If you connect multiple routers to a single subnet, however, you might need to configure more complex routing for computers on the subnet. Additionally, computers running Windows Server 2008 R2 can act as routers.

A typical intranet

A routed network with IP addresses

route add

ipconfig /setclassid

MCSA 70-642

You can use the PathPing and Tracert commands to determine how packets travel between your computer and a destination. Both tools provide similar results: PathPing provides a more detailed and reliable analysis of network performance and Tracert provides a quicker response. Notice that PathPing shows the data in two sections. The first section shows the route from the source to the destination. The second section takes longer to generate and shows the latency in milliseconds (ms) to each router. By default, Windows Server 2008 R2 does not respond to ICMP requests. This improves security, but can make troubleshooting difficult. To enable Windows Server 2008 R2 to respond to ICMP requests, run the following command at an administrative command prompt:
netsh advfirewall firewall add rule name="ICMP request" protocol=icmpv4:8,any dir=in action=allow Allow incoming V4 echo

Windows Server 2008 R2 (as well as earlier versions of Windows) supports Routing Internet Protocol (RIP) version 2, a popular routing protocol. Windows Server 2008 R2 can also forward multicast communications between subnets using the Internet Group Management Protocol (IGMP) routing protocol.

Installing Routing and Remote Access Services

To install Routing And Remote Access Services, which includes tools for configuring Windows Server 2008 R2 as a router. On the Select Server Roles page, select the Network Policy And Access Services check box, and then click Next. On the Select Role Services page, select the Routing And Remote Access Services check box. The wizard automatically selects the Remote Access Service and Routing check boxes. Click Next. In the console tree of Server Manager, expand Roles, expand Network Policy And Access Services, and then select Routing And Remote Access. Right-click Routing And Remote Access, and then choose Configure And Enable Routing And Remote Access. The Routing And Remote Access Server Setup Wizard appears. On the Configuration page, select Custom Configuration

route add

ipconfig /setclassid

MCSA 70-642

On the Custom Configuration page, select the LAN Routing check box

Configuring RIP
When you enable RIP, you allow Windows Server 2008 R2 to advertise routes to neighboring routers and to automatically detect neighboring routers and remote networks. To enable RIP, follow these steps: In Server Manager, right-click Roles\Network Policy And Access Services\Routing And Remote Access\IPv4\General, and then choose New Routing Protocol. In the New Routing Protocol dialog box, select RIP Version 2 For Internet Protocol, and then click OK. RIP, and then choose New Interface

Configuring an IGMP Proxy

IGMP multicasting transmits communications from one server to many clients. Instead of transmitting separate packets to each individual client, one packet is transmitted to all the clients simultaneously. Originally intended for streaming media, such as live video broadcasts across the Internet, IGMP is more commonly used in enterprise environments to deploy an operating system across the network to dozens of computers simultaneously. Routers have to be specially configured to forward IGMP multicasts; otherwise, they will block the multicasts from being forwarded. If you use IGMP multicasting across subnets and configure a computer running Windows Server 2008 R2 as a router, you need to configure the IGMP Router And Proxy routing protocol to forward IGMP communications between subnets. In Server Manager, right-click Roles\Network Policy And Access Services\Routing And Remote Access\IPv4\General, and then click New Routing Protocol. The New Routing Protocol dialog box appears. Select IGMP Router And Proxy, and then click OK. Routing And Remote Access adds the IPv4\IGMP node. Verify that Enable IGMP Router is selected. You should configure the interface receiving IGMP communications as the IGMP Router, and the interface forwarding IGMP communications as the IGMP proxy. In other words, the IGMP Router is closest to the server, and the IGMP Proxy is closest to the clients.

Demand-Dial Routing
Although most network connections stay active at all times, dial-up and virtual private network (VPN) connections can be connected only when a specified route is required. If you use a computer running

route add

ipconfig /setclassid

MCSA 70-642

Windows Server 2008 R2 as a router, you can configure it to establish a dial-up or VPN connection when clients attempt to communicate across a specified route (called demand-dial routing). To configure demand-dial routing, add the Network Policy And Access Services server role, configure Routing And Remote Access for demand-dial routing In Server Manager, right-click Roles\Network Policy And Access Services\Routing And Remote Access, and then click Properties. Verify that LAN And Demand-Dial Routing is selected for either or both IPv4 Router and IPv6 Router Right-click Network Interfaces, and then click New Demand-Dial Interface. The Demand-Dial Interface Wizard appears. Now, demand-dial routing will establish a connection each time any packet matches the routes you configured, and it will forward the packets across the connection. The connection will remain connected until the time-out period (5 minutes by default) expires. To test your newly configured interface by manually establishing a connection, right-click the interface, and then click Connect. The default settings such as the time-out period are rarely useful, however. Computers tend to transmit packets regularly to determine whether a connection is still active, check for updates, and announce their presence on a network. As a result, these communications keep demand-dial interfaces active even if they are not required by an application. You can use demand-dial filters to configure which communications cause Routing And Remote Access to establish a connection select either Set IP Demand-Dial Filters or Set IPv6 Demand-Dial Filters. The Set Demand-Dial Filters dialog box appears. This dialog box can be configured in two ways: to establish a connection for any communications except those you explicitly configure, and to establish a connection only when Routing And Remote Access detects specified communications. To select the Only For The Following Traffic option, first add a filter. You can further configure when Routing and Remote Access establishes connections by right-clicking the demand-dial interface and selecting Dial-Out Hours. The Dial-Out Hours dialog box allows you to configure when connections can be established. When you want the connection to remain connected permanently, right-click the interface and click Properties. Then, select Persistent Connection and click OK

Static Routing
On most networks, client computers need to be configured with a single default gateway that handles all communications to and from the subnet. Sometimes, for redundancy, network administrators might place two default gateways on a single subnet. Whether you use single or multiple default gateways, you do not need to configure static routingjust configure the default gateways using standard network configuration techniques such as Dynamic Host Configuration Protocol (DHCP).

route add

ipconfig /setclassid

MCSA 70-642

If a computer needs to use different routers to communicate with different remote networks, you need to configure static routing.

A network that requires static routing

route -p add 192.168.2.0 MASK 255.255.255.0 192.168.1.2

When using the Route Add command, the p parameter makes a route persistent. If a route is not persistent, it will be removed the next time you restart the computer. Nonpersistent routes are primarily useful for temporary troubleshooting; for example, you might add a nonpersistent route as a workaround when the primary router fails or when you are testing a new router.

The static routing table

route add

ipconfig /setclassid

MCSA 70-642

Lesson Summary
Routing allows routers to forward traffic between each other to allow clients and servers on different subnets to communicate. PathPing and Tracert allow you to identify the routers between a source and destination. Both tools are also useful for identifying routing problems. Routers use routing protocols to communicate available routes, as well as to communicate changes such as failed links. Windows Server 2008 R2 supports RIP v2, which you can enable by installing the Routing and Remote Access Services role service. You can use static routing to allow computers with multiple routers connected to their subnet to forward traffic with different destinations to the correct router.

Chapter Summary
Routing allows communications to be forwarded between subnets. On most networks, configuring computers with a default gateway is sufficient. On more complex networks with multiple routers that provide access to different remote networks, you need to configure static routing. By installing the Routing and Remote Access Services role service, you can use Windows Server 2008 R2 as a router, including the RIP version 2 routing protocol.