Windows user is limited to start/stop windows service only when logged in from SSH client.
Hi, I have configured non-admin user in Windows 2019 Server to be able to start/stop windows service. The user successfully does this by logging directly but unable to do so through Open SSH client. Installed - OpenSSH.Server~~~~0.0.1.0 net stop/start service gives this error in SSH client: System error 5 has occurred. Access is denied. As I said this happens only if the user logs on through SSH client. Any idea why this happens and is there anything to be done in OpenSSH configuration to fix this issue? Thanks!
Installing openssh client and server optional feature fails on Windows Server 2019 1809
Hello Experts, When I try to install the SSH Server and Client optional features in Windows Server 2019 it fails. They do not install. In the settings -> Manage Optional Features menu, it looks like they start but never complete and then show up back in the list of available features. This is only happening on one server. We have tried to reboot, and it did not fix the issue. SFC /scannow did not help, neither did the dism /cleanup-image /scanhealth command. Also tried installing using powershell with no luck. The powershell command add-windowsCapability -online -name OpenSSH.Server~~~0.0.1.0 appears to finish but then when we run get-WindowsCapability -online | where-object name -like 'OpenSSH*', the resultant State is "Not Present" for both client and server. Any ideas what may be wrong?ssh from hyper-v host to linux guest not working. Works perfectly from other machines. How to fix?
I have a linux guest with ssh enabled on a hyper-v host. Depending on the assigned vSwitch (Default or External), I can ssh into linux from hyper-v host but not from other systems, or I cannot ssh into linux from hyper-v host but I can from other systems. In both cases, linux can access the internet. host's IP address is 192.168.1.204. Other test machine's IP address is 192.168.1.7. Case 1: Linux on Default vSwitch, assigned address 172.23.174.5 ping from host to linux - works ssh from host to linux - works (as the network 172.23.160/20 is directly connected to host by the Hyper-V setup) ping from test to linux - will not work, since it is on another subnet ssh from test to linux - will not work, since it is on another subnet ping from linux to 8.8.8.8 - works Case 2: Linux on External vSwitch, assigned address 192.168.1.214 ping from host to linux - works!! ssh from host to linux - "Connection refused" <<<--- this is the culprit ping from test to linux - works ssh from test to linux - works ping from linux to 8.8.8.8 - works Obviously, I could go with Case 1 (NAT) and use port forwarding (netsh interface portproxy..) on the host. But I'd rather like to understand why Case 2 does not work. Especially why ping from host to linux works, but ssh does not. Any idea why this does not work and how to fix this? Dan
