SecureCRT initial telnet reconnect performance

[TheoSan]

I would like to reconnect as fast as possible into a re-booting telnet server.
I have enabled option: 'Auto reconnect' and set Auto Reconnect Interval=00000000

The SecureCRT auto reconnect option does NOT reconnect after being disconnected from the telnet server.
I can only connect AFTER i push the <enter> key in the SecureCRT session window BEFORE the server starts booting.
I would like to reconnect automatically!
All looks fine when using the option "Send protocol NO-OP" at 10sec intervals, but I do not like to waste
the bandwidth that I am using while normally connected.

I also get a window message popped-up: "Connection timed out". All telnet communication is stopped until I remove this window.
Again: I need to reconnect automatically!

Question: Is there a way to get reconnected without user interventions

[rtb]

Hi TheoSan,

Thanks for the post. It sounds like you are looking for a TCP level keepalive option. Contrary to what you might think, this is a way for a peer in a Telnet connection to determine if the other end of the connection still exists rather than trying to keep it "alive".

A peer can only know if a connection is still alive by doing something with the connection. In your case, using the Send protocol NO-OP is the way to accomplish this.

A TCP keepalive option would come with its own bandwidth overhead. Would you prefer to continue to use the existing option or would you like me to create a feature request to create a new TCP keepalive option?

[TheoSan]

Yes,
I would like a keep-alive option that is active ONLY when disconnected.
The feature turns itself OFF as soon the connection is made.

Some suggested ini-file settings:
- The disconnect time-period before the feature turns itself on
(short disconnects do not enable this)
- Interval time for sending NO-OPs while disconnected is minimal 100ms
( I need the connection as fast as possible)

[rtb]

Hi TheoSan,

The TCP level keep-alive option is the mechanism that helps SecureCRT to receive notification that the remote server has gone unresponsive.

It isn't possible to enable TCP keepalives after a connection has gone away because it is the mechanism used to determine if the connection has gone away.

The Send protocol NO-OP option described earlier is the mechanism you can use right now to both keep a connection alive longer and determine if the remote has gone unresponsive.

I have created a feature request to add a new TCP keepalives feature so reconnects can happen in a more timely manner.

We will post to this thread if the option is added to a future SecureCRT release.

If you would like to be notified directly, please complete and submit the form at the following location:

Submit Feature Request

[TheoSan]

Many thanks for creating a feature request for this