Microsoft KB Archive/169203: Difference between revisions

From BetaArchive Wiki
m (Text replacement - "<" to "<")
m (Text replacement - ">" to ">")
 
Line 65: Line 65:
<div class="indent">
<div class="indent">


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RemoteAccess\Interfaces\<Interface Number&gt;
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RemoteAccess\Interfaces\<Interface Number>





Latest revision as of 19:30, 20 July 2020

Knowledge Base


Information on Static Routes in Routing and Remote Access

Article ID: 169203

Article Last Modified on 2/27/2007



APPLIES TO

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Routing and Remote Access Service Update for Windows NT Server 4.0



This article was previously published under Q169203

SUMMARY

Static routes that are defined through the Routing and Remote Access Service (RRAS) Administrator program are not active unless the RRAS Server has started.

MORE INFORMATION

When a persistent static route is added to a system, it is stored in the following registry location:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\PersistentRoutes


This causes the static route to be entered in the route table when the IP stack is initialized. However, static routes entered using Routing and RAS Administrator on a Routing and Remote Access router are stored in a different location:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RemoteAccess\Interfaces\<Interface Number>


The value in this registry key that contains the static route is InterfaceInfo. This value contains other information as well.

Because the static route is in this location, it is not entered into the route table until the Routing and Remote Access router is initialized. Therefore, the route is not complete until the router has started.

Keywords: kbnetwork KB169203