Microsoft KB Archive/254237

= OSPF Non-Broadcast Multiple Access Neighbors Are Not Displayed When You Add Them Remotely to Windows NT 4.0-Based Router =

Article ID: 254237

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows 2000 Server

-



This article was previously published under Q254237



SYMPTOMS
When you use either the Routing and Remote Access Service snap-in or the NetShell (NetSh) utility in Microsoft Windows 2000 as the interface to remotely administer Microsoft Windows NT Server 4.0-based routers, you find that the Open Shortest Path First (OSPF) non-broadcast multiple access (NBMA) neighbors that you added to the routers are not displayed.

In addition, when you use Windows 2000 Server to remotely administer a Windows NT 4.0-based router, you find that the NBMA neighbors you added are not displayed in the Windows NT Server 4.0 Mpradmin.exe program file (Routing and RAS Admin) user interface.



CAUSE
This behavior occurs because administering OSPF NBMA neighbors in Windows 2000 requires a 'valid' interface IP address. Windows NT Server 4.0 defaults to an interface IP address of 0.0.0.0 when administering NBMA neighbors.



RESOLUTION
To work around this problem, administer NBMA neighbors locally on the Windows NT Server 4.0-based computer.



MORE INFORMATION
In a mixed Windows NT Server 4.0 and Windows 2000 environment, you can use either version of the RRAS user interface to administer NBMA neighbors, but the following limitations exist:


 * NBMA neighbors added using one user interface do not show up in the other.


 * Adding neighbors by using one user interface replaces any neighbors previously added by using the other.

Additional query words: win2krelnotes

Keywords: kbprb KB254237

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.