Why secureCRT 6.5 auto disconnect / timeout

[samuelzhan]

Why secureCRT 6.5 auto disconnect / timeout when free?
New feauture of 6.5?
It does not like this in version 6.0.

I does like this feature, how to disable?

Samuel

[bgagnon]

Hello Samuel,

I am not quite sure what you are reporting.

Are you saying you are getting frequent disconnects when idle in SecureCRT 6.5 that you did not experience in version 6.0?

Do you have any 'Anti-idle' options enabled in the 'Terminal' category of SecureCRT's Session Options?

If not, what are the results if you enable 'Send protocol NO-OP'?

Does this happen to all your connections or only to certain remotes/devices?

[samuelzhan]

Hello Brenda,

Yes, I'm getting frequent disconnects when idle in SecureCRT 6.5 by defautl setting. I did not experience in version 6.0 .
It's happen to all my connections .

If I checked "Send protocol NO-OP" in session option,
the results is following(every 60 seconds):
szux03[root]/opt/omni/sbin #^?
szux03[root]/opt/omni/sbin #^?
szux03[root]/opt/omni/sbin #^?
szux03[root]/opt/omni/sbin #^?
szux03[root]/opt/omni/sbin #^?
szux03[root]/opt/omni/sbin #^?
szux03[root]/opt/omni/sbin #^?
szux03[root]/opt/omni/sbin #^?
szux03[root]/opt/omni/sbin #^?
szux03[root]/opt/omni/sbin #^?
szux03[root]/opt/omni/sbin #^?
szux03[root]/opt/omni/sbin #^?
......

This is not what I want.
It does not disconect when idle in version 6.

Thank you very much.

Samuel.

[bgagnon]

Hello Samuel,

Thank you for the output.

From the looks of it, you have the 'Anti-idle' option 'Send string XX every ## seconds' enabled and have configured it to send a backspace.

Is 'Send protocol NO-OP every ## seconds' also enabled?

You apparently overlooked my last question:

Does this happen to all your connections or only to certain remotes/devices?

The reason I would like to know what types of connections experience disconnects is that we have a build available that resolves a known issue of intermittent disconnects when connecting to Cisco routers.

If you are connecting to Cisco routers, please contact support@vandyke.com and reference "Attn Brenda - Forum Thread #5495" in the subject line and I will make that build available to you.

If you experience disconnects to non-Cisco remotes/devices, please collect 'Trace Options' output as outlined below.

To enable trace options output:

• First, open SecureCRT's main "File" pull-down menu and select "Trace Options". If you open the "File" pull down menu again you should see a checkmark next to "Trace Options", indicating that troubleshooting output is now enabled.
  
• Next, connect to the remote machine. With trace options enabled, you will notice debugging information displayed in the terminal window that isn't normally there by default when SecureCRT is attempting to establish a connection, and at certain times throughout the lifetime of the connection.
  
• Once the problem occurs, please right-click inside the terminal window and choose "Select All", then right-click again and choose "Copy" to transfer the information to the Windows clipboard.
  
• Finally, open a text editor like 'Notepad', paste the information from the Windows clipboard into the editor program, and save it as a text file.

Since trace options can contain sensitive information, feel free to send it as an attachment via e-mail to support@vandyke.com. Please reference "Attn Brenda - Forum Thread #5495" in the subject line.

Using the above information, are you able to provide "trace options" output?

[gan]

Hello Brenda,

May i ask in what build did Vandyke resolve the "intermittent disconnects" issue?
The reason why i'm asking is because i mainly work with Cisco equipment and had some disconnects as well, but i was convinced it had to do with my network connection. Maybe my network connection is ok after all.

The build i'm currently using is 6.5.2 Build 461.

-gan

[bgagnon]

Hello gan,

The disconnect behavior has been reported in the current release (6.5.2). Based on trace provided by other customers, it looks like SecureCRT might send a data packet before the router has come back with a request for the shell.

The RFC is not specific about when it is allowable to send channel data, so this isn't exactly wrong, but it is possible it causes the router to choke.

If you would like to receive the new build, please send an e-mail to support@vandyke.com. Please reference "Attn Brenda - Forum Thread #5495" in the subject line.