Dependent LU6.2 Bind Rejected with Sense Code 0835Last reviewed: February 3, 1998Article ID: Q177899 |
The information in this article applies to:
SYMPTOMSSNA Server 3.0 (including SP1 or SP2) may reject a dependent APPC LU Bind that is sent by the host. This causes a session activation error and the following entry is made to the Microsoft Windows NT event log:
Event: 17 Description: APPC session activation failure: BIND negative response sent Sense Data = 083500xxNOTE: The xx bytes in the sense code point to the hexadecimal offset within the host bind request of the parameter that SNA Server is rejecting. In this case, the xx may point to a PLU name which may not be prepended with the network name.
CAUSEThe host system starts an LU6.2 dependent session by sending a BIND to SNA Server. If the Primary LU Name (PLU) sent in the BIND request is not preceded by the network name, then SNA Server fails to properly match against the remote APPC LU names configured in SNA Server. This causes SNA Server to reject the BIND if no network name is specified in the PLU name sent by the host system.
STATUSMicrosoft has confirmed this to be a problem in SNA Server versions 3.0, 3.0 SP1, and 3.0 SP2. This problem does not occur with SNA Server 4.0. A supported fix is now available, but has not been 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 Technical Support for more information. Keywords : kbbug3.00 kbbug3.00.sp1 prodsna snaserverservice snawinnt kbbug3.00.sp2 kbbuglist Version : WINDOWS:3.0,3.0SP1,3.0SP2 Platform : WINDOWS Issue type : kbbug Solution Type : kbfix |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |