Deploying static routing
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Deploying static routing
If static routing is appropriate for your IP internetwork, you can perform the following steps to deploy static routing:
Draw a map of the topology of your IP internetwork that shows the separate networks and the placement of routers and hosts (nonrouter computers that run TCP/IP).
For each IP network (a cabling system bounded by one or more routers), assign a unique IP network ID (also known as an IP network address).
Assign IP addresses to each router interface. It is a common industry practice to assign the first IP addresses of a given IP network to router interfaces. For example, for an IP network ID of 192.168.100.0 with a subnet mask of 255.255.255.0, the router interface is assigned the IP address of 192.168.100.1.
For peripheral routers, configure a default route on the interface that has a neighboring router. The use of default routes on peripheral routers is optional.
For each nonperipheral router, compile a list of routes that need to be added as static routes to the routing table for that router. Each route consists of a destination network ID, a subnet mask, a gateway (or forwarding) IP address, a metric (number of router hops to reach the network), and the interface to be used to reach the network.
For nonperipheral routers, add the static routes compiled in step 5 to each router. You can add static routes by using Routing and Remote Access.
When your configuration is complete, use the ping and tracert commands to test connectivity between host computers so that all routing paths are checked. For more information about the ping and tracert commands, see Using the ping command and Using the tracert command.
For information about troubleshooting static routing, see Common routing problems and Understanding the IP routing table.