
3.Most people use the preinstalled OpenSSH on Linux, however, PuTTY on Linux is used more for debugging, connecting to serial ports, and to raw sockets. Next, let’s install and set up PuTTY on Linux. If it’s missing, we can always add it: PS C:\> New-NetFirewallRule -Name 'OpenSSH-Server-In-TCP' -DisplayName 'OpenSSH Server (sshd)' -Enabled True -Direction Inbound -Protocol TCP -Action Allow -LocalPort 22 To clarify, the output shows that the firewall allows for inbound SSH traffic via Action:Allow and Direction:Inbound. Status : The rule was parsed successfully from the store. Of course, we can check to ensure the port is active: PS C:\> Get-NetFirewallRule -Name *ssh*ĭescription : Inbound rule for OpenSSH SSH Server (sshd) This opens up port 22 for inbound SSH traffic. In addition, we can configure the sshd service to start on system start-up: PS C:\> Set-Service -Name sshd -StartupType 'Automatic'Īlso, the OpenSSH Server creates and enables the OpenSSH-Server-In-TCP firewall rule. Next, we’ll proceed to start the OpenSSH Server process and prepare it for connection. Now, we’ll install the program from PowerShell with the Add-WindowsCapability command: PS C:\> Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0 The result shows that we don’t have the OpenSSH Server on our system. To do so, we need administrative access to PowerShell: PS C:\> Get-WindowsCapability -Online | Where-Object Name -like 'OpenSSH*' First, let’s check if we already have the OpenSSH Server on our system.

Now, we should see OpenSSH Server in the list.Īlternatively, we can install the OpenSSH Server from the command line. Once the process concludes, we can return to Optional features.

Search for OpenSSH Server in the search bar.Select Add a feature at the top of the page.Further, let’s select Optional features and scan the list to see if the OpenSSH Server is already installed.
