Fanfare Home | Community Home | Contact Us  

16001 -- itestcli on Windows cannot start Telnet session

Space Search
Searching iTest 3.4 Release Notes
Table of Contents

There are two causes:
 
1. In the iTestCli headless mode, terminal negotiation size is different than from the size in iTest UI mode.
In UI mode, terminal size is determined by the window size of the session. In itestcli headless
mode, the terminal size is taken from the property values on terminal size page.
2. The Windows Telnet server is in console mode. In this mode, the Windows Telnet server closes the connection if the terminal is too big.

Two workarounds:
-- Change Windows Telnet server to stream mode. It has to be in stream mode to begin with for iTest to work with it.
or
-- Change the session properties for terminal size to fixed: 80x24. This way Windows server will not close the connection due to larger terminal size.
[Show » ] Pawan Singh added a comment - 18/Jun/09 11:05 AM This is because of two reasons: 1. in iTestCli mode, the terminal negotiation size is different than in UI mode. In UI mode, terminal size is determined by window size of the session. In itestcli headless mode, the terminal size is simply the property values on terminal size page. 2. Windows telnet server is in console mode. In this mode, Windows telnet server closes connection if the terminal is too big. Two workarounds: 1. Change Windows telnet server to stream mode. It has to be in stream mode to begin with for iTest to work with it. or 2. Change the session properties for terminal size to fixed: 80x24. This way Windows server will not close the connection due to larger terminal size.

Labels

3_3_1 3_3_1 Delete
itestcli itestcli Delete
windows windows Delete
telnet_session telnet_session Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.