![]() Iirc there are keepalive settings in Putty as well that you could fiddle with.PuTTY is hands-down the best SSH client for Windows. The functionality is the same from both PuTTY and KiTTY, and happens from different internet connections, some behind a firewall, some not.Īre there any logs I can look at on the server side? I've tried all that is suggested in this thread. The SSH sessions will freeze after probably a minute of being left idle. I still haven't seen any improvement in this. Iirc there are keepalive settings in Putty as well that you could fiddle with. Did you restart sshd after modifying sshd_config? If that is the case, however, enabling the keepalive functionality should help. Rather I would guess you have a firewall/NAT "router" or something in your path that kills idle TCP connections (probably close to your end). > Are there any logs I can look at on the server side?įwiw, if I were to guess, I'd say the problem most likely isn't caused by either the client software or the server software. The functionality is the same from both PuTTY and KiTTY, and happens from different internet connections, some behind a firewall, some not. > The SSH sessions will freeze after probably a minute of being left idle. ![]() > All you Windows users, what do you use for an SSH client? ĭescription Just an update. The server side keepalive stuff only works with 2. One thought - are you configured to use version 2 of the protocol? I think in my PuTTY (which I just have around for occasional use, so it's probably an ancient version), the default SSH setting prefers protocol version 1, so maybe KiTTY inherited that. The new ssh params don't seem to have done squat. To be honest, the same SSH (OpenSSH) as on Linux, via Cygwin. > All you Windows users, what do you use for an SSH client? The server side keepalive stuff only works with 2\.įrom your original problem report it really does sound like an intermediate firewall that is timing out the connection which the keepalives, if working, should prevent. Everything just feels and looks cheap and hinky to me.ĭescription The new ssh params don't seem to have done squat. I'm sorry, but the more I browse the KiTTY website, the less I'd trust anything coming from that site or "developer". Successor or cheap knock-off, er I mean "fork"? Everything just feels and looks cheap and hinky to me. If that doesn't work, delete the registry key again and try KiTTY if that registry key is created again, then uninstall KiTTY, delete that key and figure out what the developer who felt he needed to fork perfectly good working software has screwed up. Try editing your registry and deleting HKCU\Software\SimonTatham then try PuTTY again. I wonder if KiTTY has some bad default setting. I can leave my SSH session up with PuTTY connected to my node for weeks or longer if one of the machines are not rebooted in that time frame. I've been using PuTTY since 0.48 and have had no problem on any version of Windows from 98 through Win 7, including this very second running 0.61 of PuTTY on Win7, XP and Win 2008 server. Should I just try adding these? Usually most config files will have valid options commented out, or so I've seen.ĭescription Successor or cheap knock-off, er I mean "fork"? I took a look and ClientAliveInterval and ClientAliveCountMax are not currently referenced anywhere in my sshd_config. There may be a counterpart ServerAliveInterval or something similarly named that you can set in KiTTY as well. I've found the following settings to work well for me serverside. Should I just try adding these? Usually most config files will have valid options commented out, or so I've seen. > There may be a counterpart ServerAliveInterval or something similarly named that you can set in KiTTY as well.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |