SecureCRT

PRODUCTS > SECURECRT > FAQ

Got a question or comment?

Related Links

Why does SecureCRT® timeout and close my windows on a communications event such

SecureCRT does not have any sort of "timeout" feature to automatically disconnect sessions. If you see a disconnect occur after a period of time elapses without any activity, it is not SecureCRT that is causing the disconnect. Instead, the disconnect is initiated by an idle timeout on the remote system or on a firewall/router/VPN server that resides somewhere between SecureCRT and the remote system.

Other applications like web browsers can transparently retry failed communications because they do not have to maintain an open connection. This level of transparency is not available when Telnet and SSH sessions are disconnected by an idle timeout on a remote server or a firewall/router/VPN server.

If you find your connections being disconnected after a certain period of inactivity, you can take advantage of anti-idle features in SecureCRT to try and keep connections open for longer periods of time. You can find two options in the Session Options / Terminal category: Send protocol NO-OP or Send string.

If you wish the SecureCRT window or tab to remain open even if a disconnect occurs, open the Session Options dialog, select the Terminal category, and make sure the Close on disconnect option is not enabled.

Was this information helpful?

1. Read or download one of our secure solutions white papers.

2. Download a free
30-day evaluation copy of our products.

3. Let us help define the right Secure Shell solution for your company.

4. Subscribe to our monthly newsletter for tips, solutions ideas, and product news.

SecureCRT is a registered trademark of VanDyke Software, Inc. in the United States and/or other countries. All other trademarks or registered trademarks are the property of their respective owners.