Connection Fails on SNA Server with Two Token Ring NICs

 Last reviewed: November 1, 1995
Article ID: Q129601
The information in this article applies to:
  • Microsoft Windows NT Advanced Server version 3.1
  • Microsoft Windows NT Server version 3.5
  • Microsoft SNA Server for Windows NT, versions 2.0 and 2.1

SYMPTOMS

If an SNA Server has two token ring network interface cards (NIC) and multiple SNA Server link services and connections (PU's) defined over each NIC, one or more SNA Server connections may fail to activate when the connections are started, if the remote system is located across a source routing bridge.

When an SNA Server connection is activated, SNA Server sends a TEST frame to the remote address, specifying the local network first. If no response is received, the TEST frame is resent with the "all routes" bit set. However, when this problem occurs, the second TEST frame (specifying the source routing bit) is never sent for a given connection.

CAUSE

This problem occurs when the Windows NT DLC protocol does not handle multiple token ring NICs properly.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. A fix to this problem is in development, but has not been regression-tested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Product Support Services for more information on the availability of this fix.

RESOLUTION

To correct this problem in Windows NT Server version 3.5, apply the fix.

To correct this problem in Windows NT Advanced Server version 3.1, upgrade to Windows NT Server version 3.5 and apply the fix.

KBCategory: kbinterop kbbug3.10 kbbug3.50
KBSubcategory: ntprotocol ntinterop
Additional reference words: prodnt 3.10 3.50 2.00 2.10 dlc sna prodsna

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 1, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.