IPX Routing With MPR Requires Manual Frame Type

Last reviewed: September 6, 1996
Article ID: Q142301

The information in this article applies to:

Microsoft Windows NT Server version 3.51

SYMPTOMS

After you install the Multi-Protocol Router (MPR) in Windows NT Server, Microsoft Network client computers using the IPX/SPX compatible transport protocol are unable to communicate with the Windows NT Server.

CAUSE

This problem occurs if auto frame type detection is defined for the IPX/SPX compatible transport protocol on all network adapters in the Windows NT Server. In addition, if no network numbers are assigned to network devices on the server segment, a network number of zero is assigned to all network adapters on the Windows NT Server. Therefore, all packets are not routed properly.

RESOLUTION

To correct this problem, define a manual frame type for the IPX/SPX compatible transport protocol and specify a unique network number for each segment in Windows NT Server.

KBCategory: kbnetwork
KBSubcategory: ntprotocol ntnetserv NTSrvWkst
Additional reference words: prodnt 3.51

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: September 6, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.