PuTTY Timeout
I predominantly use RDM for SSH connections.
Originally, I had my RDM set-up so that my PuTTY connections never timed-out. But recently, my PC died, so I had to move all my backed-up configs, etc, to a new computer.
Despite importing my RDM config, I am finding that my PuTTY/SSH sessions keep timing-out. It's really, really frustrating, as sometimes I have many windows open, all deep into file-systems, watching files, monitoring etc, only to get back to my workstation and find all the sessions timed-out. This definitely never used to happen before the crash/reinstall.
I have checked what RDM settings seem relevant:
- File...Options...Types...PuTTY is set to 'PuTTY'.
- My installation Path for PuTTY is also configured correctly and 'Application is ready'.
- My Default Settings... SSH Shell... General... Advanced settings have the 'Enable TCP keepalives' set, with a ping interval of 15 seconds.
- My session profiles DO NOT have the 'Automatically close session after X minutes' option set.
Can someone knowledgable in this area enlighten me on a way to fix the timeout please? :)
Thanks
All Comments (3)
Hello,
Both Putty and SSH Shell session now times out or only Putty specifically?
Best Regards,
Etienne Lord
Hello,
To be honest I'm unsure what the difference is - I was under the impression that PuTTY (the executable) is invoked when you open an "SSH Shell session" within RDM?
All of my connections use PuTTY (as far as I know), so I am guessing that the time-out is there? How can I 100% confirm this?
Something else I have also checked: my installed PuTTY exe has Connection keepalives set to every 5 seconds.
Hello,
Thank you for your swift reply!
The SSH Shell entry type uses our own in-house SSH engine while the deprecated Putty entry type uses the Putty engine. Would it be possible for you to create an SSH Shell and enter the same information used by one of your putty entries to see if the behavior is different?
Best regards,
James Lafleur