Enabling IP Routing
==================
By default, IP routing is disabled. To enable IP routing, you must allow
the computer to forward IP packets it receives. This requires a change to
the Windows 2000 system registry. When you enable the Routing and Remote
Access service for IP routing, this registry entry is made automatically.
To enable IP routing
===================
From the Start menu, click Run.
Type regedt32.exe or regedit.exe, and then click OK.
In a registry editor, navigate to HKEY_LOCAL_MACHINE
\SYSTEM\CurrentControlSet\Services\Tcpip \Parameters
Select the IPEnableRouter entry.
To enable IP routing for all network connections installed and used by this
computer, assign a value of 1. To do this in regedit.exe, right-click the
entry, and then click Modify. In regedt32.exe, click on the wanted entry,
click on Edit, and then click on the appropriate menu choice.
Close the registry editor.
Caution
========
Do not use a registry editor to edit the registry directly unless you have
no alternative. The registry editors bypass the standard safeguards
provided by administrative tools. These safeguards prevent you from
entering conflicting settings or settings that are likely to degrade
performance or damage your system. Editing the registry directly can have
serious, unexpected consequences that can prevent the system from starting
and require that you reinstall Windows 2000. To configure or customize
Windows 2000, use the programs in Control Panel or Microsoft Management
Console (MMC) whenever possible.
If the Windows 2000 router does not have an interface on a given subnet, it
needs a route to get to that subnet. This can be handled using a default
route or by adding static routes. For more information about dynamic
routing environments, see "Unicast IP Routing" in the Windows 2000
Internetworking Guide.
To add a static route, use the Route utility as follows:
route add 172.16.41.0 mask 255.255.255.0 172.16.40.1 metric 2
In this example, the route add command states that to reach the 172.16.41.0
subnet with a mask of 255.255.255.0, use gateway 172.16.40.1. It also shows
that the subnet is two hops away. You may need to add static routes on
downstream routers telling packets there how to get back to the
172.16.40.0/24 subnet.
Doug, also for more information look at Troubleshoot Ip routing article at
http://www.microsoft.com/windows2000/techinfo/reskit/samplechapters/cnbd/cnb
d_trb_vcxf.asp
Please let me know the above information fulfill your requirements.
Thanks,
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.
