On the server side, you can update the sshd_config file and set the value of the ClientAliveInterval to a non-zero value, like 60 seconds. Or you can set the ServerAliveInterval option to a similar value in your client options, either on the command line or in your local config file.
-----Original Message----- From: Soren <somia...@gmail.com> Sent: Mar 28, 2025 2:25 PM To: <cygwin@cygwin.com> Subject: sshd times out and disconnects client Hello Cygwinstas, I've got a question about the cygwin ssh daemon running on Windows. I don't know if there is a setting in sshd or in Windows that would alter the behavior I am seeing. That's what I am hoping for. When logging in from a Linux system to my Windows 10 box, there's a timeout (of what duration, I am not precisely sure, maybe after 2 hours?) if I am not doing anything over the ssh connection. The session is disconnected at the server end. I find this a bit annoying. I might want to be doing something else for a couple hours and then come back to the session, only to find it's disconnected. This is in contrast to the reverse case, where I am logging in to one of my Linux boxes from Windows: in that case, the connection stays alive until I deliberately close it. The same with sessions between Linux machines. It's only in the case of incoming connections to sshd on cygwin/windows that I am seeing this. Insights greatly appreciated. Regards, Your fellow loyal Cygwinista, Soren Andersen -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
