Microsoft KB Archive/126393

= SNA Server configurations that produce XID rejections =

Article ID: 126393

Article Last Modified on 4/28/2005

-

APPLIES TO


 * Microsoft Host Integration Server 2000 Standard Edition
 * Microsoft SNA Server 2.0
 * Microsoft SNA Server 2.1
 * Microsoft SNA Server 3.0
 * Microsoft SNA Server 2.11 Service Pack 1
 * Microsoft SNA Server 3.0 Service Pack 4
 * Microsoft SNA Server 4.0
 * Microsoft SNA Server 3.0 Service Pack 2
 * Microsoft SNA Server 3.0 Service Pack 3
 * Microsoft SNA Server 3.0 Service Pack 4
 * Microsoft SNA Server 4.0
 * Microsoft SNA Server 4.0 Service Pack 1
 * Microsoft SNA Server 4.0 Service Pack 2
 * Microsoft SNA Server 4.0 Service Pack 3
 * Microsoft SNA Server 4.0 Service Pack 4

-



This article was previously published under Q126393



SUMMARY
The following SNA Server XID rejection events are logged in the application event log when you connect to an AS/400:
 * Event ID: 56 Event description: Connection  failed: XID rejected by remote computer
 * Event ID: 230 Event Description: Connection  Not responding to XID commands.

The connection goes into a Pending state and users get APPC primary return code: 0003; secondary return code: 00000005, when attempting to open a 5250 session.

Causes of Event ID 56:


 * There is already a controller defined on the AS/400 with the same name as the one defined in SNA Server, but it has a different "LAN remote adapter address (ADPTADR)" associated with it.
 * There is already a different controller name defined on the AS/400 with the same "LAN remote adapter address (ADPTADR)" (Autocreate Controller [AUTOCRTCTL] is set to YES in the AS/400 Line Description).
 * The "LAN remote adapter address (ADPTADR)" defined on the AS/400 represents the network interface card address of the SNA Server computer. To determine this, type the following at a Windows NT Command Prompt: c:> net config server
 * The Remote Control Point Name in the SNA Server Administrator Connection Properties dialog box does not match the Local Control Point Name in the AS/400 Network Attributes screen.

Causes of Event ID 230:
 * Autocreate controller (AUTOCRTCTL), which is configured in the AS/400 Line Description, is set to No and you are using the incorrect Local Node ID value for the controller you have manually created on the AS/400.
 * The Remote SAP Address in the SNA Server connection properties is different than the SSAP address in the AS/400 line description.

NOTE: The SAP address defined in the SNA Server link service setup does not have to match anything on the AS/400.
 * The administrator configured the Remote Network Address using an address that already exists on the LAN (and is bound to the DLC protocol) but it is not the address that the AS/400 administrator is attempting to connect to. For example, an administrator used the SNA Server machine address or other Windows NT machine that has the MS-DLC protocol installed.

Additional query words: HIS 2000 prodsna nic adapter admin snafaq

Keywords: kbinfo kbnetwork KB126393

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.