SecureCRT 8.3b4: sessions gone after Windows resumes from sleep mode

[renep]

When I have several SecureCRT sessions open in 8.3.0 beta 4 (x64 build 1509), and Windows 10 enters sleep mode (not just the screen, the entire PC) and I wake it up, SecureCRT is still running but all my SecureCRT sessions are gone (I see an empty window with only the session manager). On the Linux server, a user process such as vi is still running.

I get the same behaviour with Version 8.3.0 (x64 build 1491) on another Windows 10 PC.

I'm not sure, but I don't remember this behaviour from previous versions. I seem to remember that SecureCRT sessions would still be active. Is this perhaps an issue in the beta version?

[berdmann]

When I have several SecureCRT sessions open in 8.3.0 beta 4 (x64 build 1509), and Windows 10 enters sleep mode (not just the screen, the entire PC) and I wake it up, SecureCRT is still running but all my SecureCRT sessions are gone (I see an empty window with only the session manager). On the Linux server, a user process such as vi is still running.

I get the same behaviour with Version 8.3.0 (x64 build 1491) on another Windows 10 PC.

I'm not sure, but I don't remember this behaviour from previous versions. I seem to remember that SecureCRT sessions would still be active. Is this perhaps an issue in the beta version?

Can you describe in detail the steps to reproduce this behavior?

Are you viewing your sessions in tabs or tiles?

Are you saying that as soon as you wake up your computer that the SCRT window is still open but the tabs/tiles of the sessions that were connected are no longer there?

Did you recently make any changes to your SCRT settings?

[renep]

Originally Posted by berdmann

Can you describe in detail the steps to reproduce this behavior?

• I start SecureCRT 8.3b4, open some sessions to multiple servers
• Windows 10: Windows button > Power button > Sleep mode
• Wake up the PC, unlock the screen
• Stare at empty SecureCRT without active sessions

Are you viewing your sessions in tabs or tiles?

In tiles (vertically), or tabs. With the same behaviour.

Are you saying that as soon as you wake up your computer that the SCRT window is still open but the tabs/tiles of the sessions that were connected are no longer there?

Exactly.

Did you recently make any changes to your SCRT settings?

I enabled "Connect multiple sessions sequentially" as suggested by JJH.

I changed Configuration Path to another network-mapped drive. Could that cause SecureCRT to close/loose sessions?

I can't think of any other changes right now, but I'm not entirely sure.

[berdmann]

Hi Renep!

Thank you for the additional information!

It sounds like you may have "Close on Disconnect" enabled.

Please go to Options > Session Options > Terminal and disable "Close on Disconnect".

After making this change you should see your tabs in the SCRT window after your PC resumes from sleep mode, however the sessions will not be connected.

If you would like your sessions to automatically reconnect upon resuming from sleep please go to Options > Global Options > Terminal and enable "Auto Reconnect".

Does this information render the behavior you are looking for?

[renep]

Hello Brittney,

Originally Posted by berdmann

Please go to Options > Session Options > Terminal and disable "Close on Disconnect".

Okay, I did that.

After making this change you should see your tabs in the SCRT window after your PC resumes from sleep mode, however the sessions will not be connected.

Yes, that's right. With the consequence that e.g. vim sessions on the server that were running when the PC went into sleep mode are hanging as an orphaned process without a conected terminal, and a long running backup script failed when it attempted ssh authentication.

Does this information render the behavior you are looking for?

Well no, not really. I seem to remember that SecureCRT behaved differently in the past, and terminal sessions remained connected when the PC came out of sleep mode. E.g. you could simply continue in a runing vim session.

But I cannot reproduce that behaviour, not with 8.1.4, not with various configurations. Am I mistaken and were connections always dropped by Windows sleep mode

[berdmann]

Hi Renep!

By default, SecureCRT is designed to disconnect sessions after resuming from sleep.

The following Global.ini only option can be used to prevent sessions from being disconnected when the PC is resumed from sleep mode:

"Disconnect After Resume Timeout"

Please go to C:\Users\username\AppData\Roaming\VanDyke\Config (This is the default Config path, you can view your Config path by going to Options > Global Options > Configuration Paths)
and change the "Disconnect After Resume Timeout" value to "ffffffff"

Does changing this setting in your Global.ini allow your session to remain active upon resuming from sleep?

[renep]

Originally Posted by berdmann

Does changing this setting in your Global.ini allow your session to remain active upon resuming from sleep?

Yes, it does. Thank you.

Behaviour with this setting is how I remember it from ... sometime in the past. I'm still slightly confused, since I haven't enabled this setting previously, as far as I can remember.

[berdmann]

Rene,

I am glad that setting the "Disconnect After Resume Timeout" value to "ffffffff" in your Global.ini did the trick!

In SecureCRT versions 6.5 and earlier the default behavior was to remain connected upon resume from sleep. The Global.ini "Disconnect After Resume Timeout" setting would need to be adjusted manually to achieve this behavior in all versions released after 6.5.

[renep]

Originally Posted by berdmann

In SecureCRT versions 6.5 and earlier the default behavior was to remain connected upon resume from sleep. The Global.ini "Disconnect After Resume Timeout" setting would need to be adjusted manually to achieve this behavior in all versions released after 6.5.

Aha, that explains it. Thanks for clarifying

[berdmann]

I am happy to help!

Have a great day!