Microsoft KB Archive/128986: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
Line 25: | Line 25: | ||
When connecting from an SNA Server client using the TCP/IP sockets interface to SNA Server, the following problems may occur if the Windows NT TCP/IP Protocol is bound to more than one network card on the server, and different IP addresses are configured for each card: | When connecting from an SNA Server client using the TCP/IP sockets interface to SNA Server, the following problems may occur if the Windows NT TCP/IP Protocol is bound to more than one network card on the server, and different IP addresses are configured for each card: | ||
* When opening a 3270 session, the session may never activate (the SNA 3270 applet may display | * When opening a 3270 session, the session may never activate (the SNA 3270 applet may display "No SNA Server found in domain" on the status line). | ||
* When opening a 5250 session, an APPC error may occur (F004 - or AP_COMM_SUBSYSTEM_NOT_LOADED). This indicates that the SNA client could not locate a running SNA Server in the domain which supports the local and remote LU aliases being requested. | * When opening a 5250 session, an APPC error may occur (F004 - or AP_COMM_SUBSYSTEM_NOT_LOADED). This indicates that the SNA client could not locate a running SNA Server in the domain which supports the local and remote LU aliases being requested. | ||
* If multiple SNA Servers are configured the same way, the client may not be able to open a session through one or more of the servers, but not all. | * If multiple SNA Servers are configured the same way, the client may not be able to open a session through one or more of the servers, but not all. | ||
NOTE: A network trace will indicate that the IP router is returning an | NOTE: A network trace will indicate that the IP router is returning an "ICMP Destination Unreachable" message to the SNA client's connection request. | ||
<br /> | <br /> | ||
Line 36: | Line 36: | ||
When SNA Server is configured (using SNA Setup) to accept client sessions over TCP/IP sockets, SNA Server only searches for the first IP address that is configured on the server. The first IP address corresponds with the first adapter that the Windows NT TCP/IP Protocol is bound to.<br /> | When SNA Server is configured (using SNA Setup) to accept client sessions over TCP/IP sockets, SNA Server only searches for the first IP address that is configured on the server. The first IP address corresponds with the first adapter that the Windows NT TCP/IP Protocol is bound to.<br /> | ||
<br /> | <br /> | ||
When an SNA client opens its | When an SNA client opens its "sponsor connection" to an SNA Server in the domain, SNA Server sends down the server name and IP address it finds. However, the SNA client may not be able to connect to the server over this first IP address since the IP address may only be available over the other server's network card. | ||
<br /> | <br /> | ||
Line 49: | Line 49: | ||
*# Choose the Bindings button | *# Choose the Bindings button | ||
*# Select the TCP/IP Protocol and choose OK | *# Select the TCP/IP Protocol and choose OK | ||
*# Select the desired adapter and choose the | *# Select the desired adapter and choose the "up" arrow button on the right side of the Network Bindings dialog. Move the adapter to make it the first in the list. | ||
*# Choose OK.<br /> | *# Choose OK.<br /> | ||
<br /> | <br /> | ||
NOTE: It doesn't matter which SNA Server in the domain is providing the | NOTE: It doesn't matter which SNA Server in the domain is providing the "sponsor connection" for the SNA client software (the sponsor server is indicated when installing the SNA client software within the "primary" and "backup" servers when the "remote domain" option is selected). The client sponsor connection will work against either of these servers. However, this problem will prevent the client from opening a 3270 or APPC session through the servers. | ||
<br /> | <br /> |
Latest revision as of 14:31, 20 July 2020
The information in this article applies to:
on the following platforms: NT
SYMPTOMSWhen connecting from an SNA Server client using the TCP/IP sockets interface to SNA Server, the following problems may occur if the Windows NT TCP/IP Protocol is bound to more than one network card on the server, and different IP addresses are configured for each card:
NOTE: A network trace will indicate that the IP router is returning an "ICMP Destination Unreachable" message to the SNA client's connection request.
CAUSEWhen SNA Server is configured (using SNA Setup) to accept client sessions over TCP/IP sockets, SNA Server only searches for the first IP address that is configured on the server. The first IP address corresponds with the first adapter that the Windows NT TCP/IP Protocol is bound to.
RESOLUTION
STATUSMicrosoft has confirmed this to be a problem in SNA Server 2.1. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. Additional query words: prodsna 2.10 tcp/ip sockets Keywords : Version : WINDOWS:2.1 Platform : WINDOWS Issue type : |
Last Reviewed: September 17, 1999 |