5 SSH Client for Windows to SSH Tunneling into Linux Machines

If you are looking for a way to SSH into Linux machines with your Windows computer, here are 5 SSH Windows Clients for your to choose. Other than the first one listed below which is exclusive to Windows 10, the other ones

Windows Subsystem

If you are using Windows 10 and have enabled Windows Subsystem Bash and are running Ubuntu distro natively on your computer, you have the ability to SSH in without other tools.

Open Ubuntu on your Windows 10, log in with your own credential and then ssh.

ssh login_name@hostname

SSH from Windows Subsystem Ubuntu

OpenSSH for Windows

OpenSSH is an open source project made by the PowerShell team as an attempt to support SSH.

Download the latest release in ZIP format and extract the content to a folder. Then all you need is to open a Command Prompt window, navigate to that folder and run ssh.

ssh login_name@hostname

PuTTy

PuTTy is probably the SSH client used the most on Windows. It’s a portable free tool that supports not only SSH but Telnet, Xterm as well. It’s also a simple and easy-to-use tool as well. Simply put in the hostname and click Load button to start.

PuTTy

Bitvise

Bitvise offers both SSH Server and SSH Client for Windows Servers and workstations. The SSH Client is free with a graphical interface as well as command-line SFTP support, a FTP-to-SFTP bridge, powerful tunneling features including dynamic port forwarding through an integrated proxy, and remote administration for our SSH Server.

Bitvise - main window

SmarTTY

Unlike PuTTy or Bitvise, SmarTTY is a free multi-tabbed SSH client that also supports copying files and directories with SCP on-the-fly and editing files in-place.

SmartTTY

Because it’s a tab-based SSH client, it makes a no-brainer to go with if you need to open multiple sessions on your Linux machines. No annoying multiple windows, no need to re-login, just open a new tab and here you go.

That’s all for now. If you have other preferences not listed here, please share them in the comment.

Source