Greetings:

Question #1: I recently upgraded from 3.3.0 to 3.3.2 that contains the SSH support. The default is supposed to be that telnet connections will use the 'NON SECURE' protocol setting. However, as soon as I made the upgrade, none of my telnet session jobs could connect, they all timed out at 90 seconds(my choice for timeout setting). Since this box is in production, I immediately stripped 3.3.2 off and installed 3.3.0, problem gone. I didn't want the jobs to be down long enough to edit and test.

Do you have to specify the 'NON SECURE' protocol? The documentation says it is the default.

Question #2: Does the 'TelnetClose' command automatically send an 'exit' string to the host or should that be done immediately prior to issuing that command? I seem to be getting a lot of shell sessions on our Unix boxes, that are initiated by this system, that never close out.

Thanks!

Neil.....

If you have tracing option enabled check in the Telnet.log which operation caused the connection to time out.

You do not have to specify the 'NON SECURE' protocol. This is the default, however if you use other TelnetConfig settings such as PORT and PROTOCOL make sure to specify PROTOCOL first and then PORT.

TelnetClose does not send the Exit, it simply closes the session on the client. Works the same as closing the standard Telnet terminal screen. It does not send the Exit, or does it?

: Greetings: Question #1: I recently upgraded from 3.3.0 to 3.3.2 that contains
: the SSH support. The default is supposed to be that telnet connections
: will use the 'NON SECURE' protocol setting. However, as soon as I made the
: upgrade, none of my telnet session jobs could connect, they all timed out
: at 90 seconds(my choice for timeout setting). Since this box is in
: production, I immediately stripped 3.3.2 off and installed 3.3.0, problem
: gone. I didn't want the jobs to be down long enough to edit and test.

: Do you have to specify the 'NON SECURE' protocol? The documentation says it
: is the default.

: Question #2: Does the 'TelnetClose' command automatically send an 'exit'
: string to the host or should that be done immediately prior to issuing
: that command? I seem to be getting a lot of shell sessions on our Unix
: boxes, that are initiated by this system, that never close out.

: Thanks!

: Neil.....

: If you have tracing option enabled check in the Telnet.log which operation
: caused the connection to time out.

: You do not have to specify the 'NON SECURE' protocol. This is the default,
: however if you use other TelnetConfig settings such as PORT and PROTOCOL
: make sure to specify PROTOCOL first and then PORT.

: TelnetClose does not send the Exit, it simply closes the session on the
: client. Works the same as closing the standard Telnet terminal screen. It
: does not send the Exit, or does it?

Are you not positive?

I am possitive about TelnetClose, but not whether closing the regular Terminal window sends the exit command. Anyway, I know for sure the TelnetClose causes the client session to send the low-level protocl BUY message indiating end-of-session and then close the Winsock connection.

: Are you not positive?

: If you have tracing option enabled check in the Telnet.log which operation
: caused the connection to time out.

The logging says the last function before the timeout notification is the TelnetOpen statement. I've installed onto another box and copied the daabase over, same thing. Now what?

: You do not have to specify the 'NON SECURE' protocol. This is the default,
: however if you use other TelnetConfig settings such as PORT and PROTOCOL
: make sure to specify PROTOCOL first and then PORT.

: TelnetClose does not send the Exit, it simply closes the session on the
: client. Works the same as closing the standard Telnet terminal screen. It
: does not send the Exit, or does it?

This appears to be a regression bug in 24x7 which was introduced either in 3.3.1 or 3.3.2.

As an emergency fix we will be releasing tomorrow version 3.3.4 that includes fixes for Telnet, Database Summary report and some other recently found bugs.

: The logging says the last function before the timeout notification is the
: TelnetOpen statement. I've installed onto another box and copied the
: daabase over, same thing. Now what?

This is fixed in 3.3.4. Please see http://www.softtreetech.com/cgi_bin/config.cgi?read=2921 for details.

: This appears to be a regression bug in 24x7 which was introduced either in
: 3.3.1 or 3.3.2.

: As an emergency fix we will be releasing tomorrow version 3.3.4 that includes
: fixes for Telnet, Database Summary report and some other recently found
: bugs.