The information in this article applies to:
SYMPTOMSTelnet 3270 clients may experience a long delay when starting sessions. This symptom is observed when a DNS Server is not available. CAUSEIn the event a DNS Server is not available and Use Name Resolution is configured, a Telnet client will experience a delay of up to 50 seconds during session startup. The SNA Server expects a response from the DNS Server. SNA Server will delay the session until a timeout is reached. RESOLUTIONThe TN3270 Server Service contains a configuration option titled "Use Name Resolution". Use Name Resolution is found on the General tab of the TN3270 Properties dialog box. Use Name Resolution is required if access to TN3270 sessions is restricted through workstation names. It is not required if access to TN3270 sessions is restricted through a TCP/IP address or subnet. This option should be checked only if a domain name resolver is available on the network. MORE INFORMATION
A Microsoft Network Monitor trace shows the Telnet client and SNA Server performing a three-way TCP handshake to initiate the session within 0.003 seconds. A delay in excess of 45 seconds occurred before the Telnet session was available to the client.
Here is an example of the first two frames in the Telnet session. These frames will be delayed from the first three frames by 45 seconds or more.
Additional query words:
Keywords : kbenv kbnetwork |
Last Reviewed: February 9, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |