Closed tfenster closed 4 years ago
I think it's specific to your environment. SSHD process is being killed by other process.
I just tried with V8.1, I didn't see any issue. Please get V8.1 and try in your environment to confirm this.
I've tried with 8.0.1 and the problem still exists.
SSHD process is being killed by other process.
Do you mean to say that the server side is killed? That is actually not true, I can immediately reconnect after the error happens
@tfenster Not saying that @bagajjal is definitely correct, but some pieces of security software (for example) will forcefully kill inactive connections. Whenever you connect you get your own dedicated sshd.exe process that hosts your sessions so being able to immediately reconnect is not necessary mean something isn't killing the process associated with your session.
"OpenSSH for Windows" version
((Get-Item (Get-Command sshd).Source).VersionInfo.FileVersion)
7.7.2.1Server OperatingSystem
((Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows nt\CurrentVersion\" -Name ProductName).ProductName)
Windows Server 2019 Datacenter (Windows Server Core)Client OperatingSystem Windows Version 2004 (Build 19041.172)
What is failing I can use openssh fine until I leave the terminal where it is running alone for a couple of minutes and don't interact with the session. After that I see
Expected output The connection to sshd keeps open
Actual output The connections breaks
Debug output from the server
No new debug output happens when the client disconnects
Debug output from the client