Hey Matt, Thanks for posting this. It was very helpful and I was able to confirm I was doing the steps I had pieced together. I still get the "subsystem request failed on channel 0" error. I am having little luck finding useful help. So, if you have seen this, any help would be appreciated. From: Windows 2012 R2 w/PWSH 6.1 To: Palo Alto 3050 Validated: Port 22 was open to firewall Username and Password are correct New-Item -ItemType SymbolicLink -Path c:\pwsh -Value "C:\Program Files\PowerShell\6" -Force "Subsystem powershell c:\pwsh\pwsh.exe -sshs -NoLogo -NoProfile" was added "C:\Program Files\OpenSSH\" is in the Environment PATH The kicker is SSH.exe works fine to the same machine. I know the warning is about the Subsystem, but I am at a loss on what to change to fix it. If you are not familiar, no worries... just asking incase you might know Jason W.
Hi Jason. The only way I got around the "subsystem request failed on channel 0" was to follow those steps in the video. I'm sure you did, but I have to ask, did you make sure to restart the sshd service after modifying the sshd_config file? If so, I might have to see if I can do some digging on this. I also haven't tried this yet with the latest version of PowerShell 6.1 so I wonder if that could have something to do with it. I'd have to try it out.
I just installed the latest stable version of PowerShell and the latest version of OpenSSH and was able to connect without getting the subsystem error so I'm not sure what could be going on.
what is the benefit of using PS-Session over using ssh client to server?
good question
Hey Matt,
Thanks for posting this. It was very helpful and I was able to confirm I was doing the steps I had pieced together. I still get the "subsystem request failed on channel 0" error. I am having little luck finding useful help. So, if you have seen this, any help would be appreciated.
From: Windows 2012 R2 w/PWSH 6.1
To: Palo Alto 3050
Validated:
Port 22 was open to firewall
Username and Password are correct
New-Item -ItemType SymbolicLink -Path c:\pwsh -Value "C:\Program Files\PowerShell\6" -Force
"Subsystem powershell c:\pwsh\pwsh.exe -sshs -NoLogo -NoProfile" was added
"C:\Program Files\OpenSSH\" is in the Environment PATH
The kicker is SSH.exe works fine to the same machine. I know the warning is about the Subsystem, but I am at a loss on what to change to fix it.
If you are not familiar, no worries... just asking incase you might know
Jason W.
Hi Jason. The only way I got around the "subsystem request failed on channel 0" was to follow those steps in the video. I'm sure you did, but I have to ask, did you make sure to restart the sshd service after modifying the sshd_config file? If so, I might have to see if I can do some digging on this. I also haven't tried this yet with the latest version of PowerShell 6.1 so I wonder if that could have something to do with it. I'd have to try it out.
Matt McElreath I did, but have since learned that they are deprecating the pwsh -sshs switch. I wonder if the have broke it with 6.1
I just installed the latest stable version of PowerShell and the latest version of OpenSSH and was able to connect without getting the subsystem error so I'm not sure what could be going on.