If No Session Configured, TN3270 Client Error Can Be Misleading (149302)



The information in this article applies to:

  • Microsoft SNA Server 2.11, when used with:
    • the operating system: Microsoft Windows NT
  • Microsoft SNA Server 3.0, when used with:
    • the operating system: Microsoft Windows NT
  • Microsoft SNA Server 4.0, when used with:
    • the operating system: Microsoft Windows NT

This article was previously published under Q149302

SYMPTOMS

If no LUs are defined in the TN3270 Server configuration, or you have a pool with zero sessions, the following error message returned to the client can be misleading:
The primary error message is an event 511:
Telnet negotiation failure: client did not send term type.
This can cause some confusion as why you are unable to establish a session.

RESOLUTION

Define LUs in the TN3270 Server configuration on SNA Server 2.11, or assign LUs to a TN3270 Server in SNA Server Manager on SNA Server 3.0. Verify that LUA pools used by the TN3270 servers contain valid LUs.

MORE INFORMATION

A trace shows the client and server going into a loop trying to establish its terminal type, and finally the TN3270 server terminating the session. This happens because the client did not send the correct terminal type. Because no LUs are configured, there is no way it can ever send the correct terminal type.

Modification Type:MinorLast Reviewed:3/8/2005
Keywords:kbnetwork KB149302