keep history while connection issues

[Jackson1]

hello,

I have been using SecureCRT since almost 20 years and one thing always annoyed me:

- lets say you are connected to a SSH session and work as usual
- now you might have bad internet connection (mobile internet in the train, for example)
- you get disconnected randomly, maybe just for a few seconds, but could be aswell 10-20min.
- I have autom. connection retry enabled for all sessions
- so they keep trying to connect, but too bad, my hotel WiFi broke down or my train is stuck in a tunnel
- now what happens is that SecureCRT will fail to connect and post something like this into the session window:

Connection timed out


Press Ctrl+C to cancel or Enter to reconnect immediately.
Reconnecting in 1 seconds...

- so far so good, this keeps going on every X seconds until your internet is back
- meanwhile this redundant connection error messages will push your history out of existence
- especially because each connection error message is a whole screen/page, with lots of blank lines
- a few minutes without internet will wipe out all your history/screen buffer - and flood it with the same error messages - ouch!
- now you can't even look what you did just before the connection broke, or maybe you were running some updates and at some point they broke the server, but you can't even see what happened, because your screen buffer is flooded with these error messages while you were 5min away for coffee.

ideas:
- dont show redundant error messages while trying to connect, just update the same message/screen
- do not pollute the history/screen buffer with redundant error messages
- overwrite the old error message at the same position on the screen/history with the new error message

looking forward to hear other ideas/opinions.
thanks you!

[ekoranyi]

Hi Jackson1,

Thanks for the feedback. I was able to reproduce the behavior you're describing.

I have recorded your idea in our database of SecureCRT feature requests so that the product director can evaluate it for possible inclusion in a future release.

Should a version of SecureCRT become available with this feature, we will be sure to let you know.

[Jackson1]

any news on this? sounds like an easy fix...

[berdmann]

Hi Jackson1,

We do not have any news regarding this feature request.

Feature requests are typically prioritized based on a number of factors including, but not limited to, the number of requests and the amount of implementation work required.

We will be sure to post here to notify you if the feature is implemented in a future release of SecureCRT.

[Jackson1]

1 year went by... and nothing :-(

I have another request, made almost 2 years ago, and also nothing.

So please help me to find a reason to pay your "3 Yrs of Updates" again when it expires next year.

[Maureen]

I'm sorry we haven't been able to address this in a timely fashion. To date, you are the only customer who has reported this issue to us.

That said, I can see how it would be annoying and I will check with the programmers to see if it's something we can address in the next version.

In the meantime, a workaround might be to log the session so that you could see what was happening before the connection was lost.

Regards,
Maureen

[berdmann]

Hi Jackson1,

Maureen wanted me to let you know that a fix has been implemented to prevent connection time out errors from overwriting scrollback buffer output.

If you would like to test the fix, please send an email to support@vandyke.com with ***ATTN: Brittney, Forum Thread #13079*** in the subject line.

[Jackson1]

Only saw this now!

Wow, it has been fixed, beautiful!!

From my testing so far it seems to be working fine in v8.7.1

Many, many, many thanks!

[berdmann]

Hi Jackson1,

I am pleased to hear that you were able to verify that SecureCRT 8.7.1 prevents connection time-out errors from overwriting scrollback buffer output! Thanks for sharing your feedback!