SNA Server Retrieves Incorrect Net Name from XID (276036)

The information in this article applies to:

Microsoft SNA Server 3.0 SP1
Microsoft SNA Server 3.0 SP2
Microsoft SNA Server 3.0 SP3
Microsoft SNA Server 3.0 SP4
Microsoft SNA Server 4.0
Microsoft SNA Server 4.0 SP1
Microsoft SNA Server 4.0 SP2
Microsoft SNA Server 4.0 SP3

This article was previously published under Q276036

SYMPTOMS

Under certain circumstances, SNA Server needs to retrieve the Network Name from the XID frames (sent at connection activation), in order to build a Remote Advanced Program-to-Program Communications (APPC) Logical Unit (LU) Definition when the Supports Dynamic Remote APPC LU Definition feature is enabled in host connection properties.

SNA Server may use an incorrect value as the Network Name, which causes BIND requests to be rejected by the Host with an UNBIND (Cleanup).

CAUSE

SNA Server specifically checks for the first occurrence of a "0E" vector and assumes that it is the CPName field ("F4" subvector). A XID frame can include several "Network Name" Control Vectors (code 0x0E); the first one usually starts at position 0x1D in the frame. For each control vector 0x0E, byte 2 indicates the "Network name type;" 0xF1 = PU Name, 0xF4 = CP Name, and 0xF7 = local ALS name.

SNA Server assumes that the first 0x0E control vector is the CP name, type 0xF4. When this is not the case, SNA Server uses an incorrect value as the Network Name.

RESOLUTION

To resolve this problem, obtain the latest service pack for SNA Server 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was first corrected in SNA Server 4.0 Service Pack 4.

Modification Type:	Major	Last Reviewed:	6/25/2004
Keywords:	kbbug kbfix kbQFE kbSNA400PreSP4fix kbSNA400sp4fix KB276036