Autostatic Route Updates Fail Over IPX

 Last reviewed: November 21, 1997
Article ID: Q168578
The information in this article applies to:
  • Microsoft Windows NT Server version 4.0
  • Routing and Remote Access Service Update

SYMPTOMS

After you issue several Update Routes commands from the Routing and Remote Access Service server, the IPX network number of the WAN link gets changed from all zeros to a number other than zero. This causes the Routing and Remote Access Service server to drop all Routing Information Protocol (RIP) & Service Advertising Protocol (SAP) packets coming from the remote router. You then lose all connectivity to the other router and the networks it is connected to.

CAUSE

The router defaults to unnumbered WAN links with Routing and Remote Access Service for Windows NT Server 4.0. If the Network number for the remote router changes to anything other than all zeros the local router will drop all RIP and SAP packets from the remote router.

For example: 

   From the local router, right-click Summary under IPX Routing. Then
   select Update Routes. After doing this several times, the Network
   number for the remote router may become something other than all zeros.
   The local router will then drop any RIP & SAP packets received from the
   remote router. Update Routes will no longer work.
To verify you are seeing this problem, do the following. Go to a command prompt on each router and type: 

   C:\ipxroute config
You should see something similar to this depending on how many network cards are installed, etc. 

   NWLink IPX Routing and Source Routing Control Program v2.00

   net 1: network number 00002602, frame type 802.2, device El59x1
   (00c04fc29c12)
   net 2: network number 00002602, frame type ethernet ii, device
   NdisWan10 (f4aa8a000000)+ active wan line
If the NdisWan device's network number is something other than all zeros, then you are experiencing this problem.

This is how it should look: 

   NWLink IPX Routing and Source Routing Control Program v2.00

   net 1: network number 00002602, frame type 802.2, device El59x1
   (00c04fc29c12)
   net 2: network number 00000000, frame type ethernet ii, device
   NdisWan10 (f4aa8a000000)+ active wan line
an HKEY_LOCAL_MACHINE\system\currentcontrolset\services\remoteaccess

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next service pack that contains this fix. Contact Microsoft Product Support Services for more information.

Additional Reference words: prodnt rras 

Keywords          : kbbug4.00 kbfix4.00 ntrouter NTSrv kbnetwork
Version           : WinNT:4.0
Platform          : winnt
Issue type        : kbbug

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 21, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.