SNA Server Admin Lists Wrong Dependent APPC LU as "In Session"

 Last reviewed: February 1, 1996
Article ID: Q140835
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, versions 2.0, 2.1, and 2.11

SYMPTOMS

An SNA Server that has a local dependent APPC (LU6.2) session partnered with multiple remote LUs shows that the wrong LU is "In Session".

This problem occurs sporadically.

CAUSE

When SNA Server receives an unsolicited BIND for a dependent APPC LU, it does not check the names in the BIND. SNA Server assumes that it is a BIND for an LU on that LU address. However, if a local dependent APPC LU is partnered with more than one remote LU, SNA server is in effect choosing at random which LU it believes the BIND to be from.

RESOLUTION

SNA Server has been modified so that it does examine the LU names in an unsolicited BIND it receives for dependent APPC LUs.

Microsoft has updated the following files to correct this problem: 

   <snaroot>\SYSTEM\SNASERVR.EXE
   <snaroot>\SYSTEM\TRCSERVR.EXE

STATUS

Microsoft has confirmed this to be a problem in SNA Server for Windows NT. This problem was corrected in the latest SNA Server for Windows NT, 2.11 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

KBCategory: kbnetwork kbbug2.00 kbbug2.10 kbbug2.11
KBSubcategory: ntnetserv
Additional reference words: prodsna 2.00 2.10 2.11 3.50 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: February 1, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.