Autostatic Route Updates Failing


--------------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Windows NT Server version 4.0
 
--------------------------------------------------------------------------


SYMPTOMS
========

After issuing several Update Routes commands from the Routing and Remote
Access 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 Server to drop all RIP & SAP packets coming from the remote router.
This causes you to 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
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.   


Example: From the Local Router select 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

 


STATUS
======

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A 
supported fix is now available, but is not 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.