Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing WinSSHTerm vs mRemoteNG, the Slant community recommends WinSSHTerm for most people. In the question“What are the best SSH clients for Windows?” WinSSHTerm is ranked 15th while mRemoteNG is ranked 18th. The most important reason people chose WinSSHTerm is:
WinSSHTerm is free for anyone to use.
Question Ranking
Pros
Pro Freeware
WinSSHTerm is free for anyone to use.
Pro Keyboard shortcuts
Keyboard shortcuts are especially valuable for professionals.
Pro Supports X Server
There is easy, automatic integration with X Server and starts/stops can take place with the launch/exit of WinSSHTerm.
Pro Supports file transfer
The user can start a WinSCP session inside WinSSHTerm, without the need to duplicate the session in WinSCP.
Pro Highly portable
The user can run WinSSHTerm from a USB drive on different computers.
Pro Ready for production use
There are no annoying bugs in WinSSHTerm. Navigation tools and keyboard shortcuts are a great time saver, especially if you have to manage multiple connections.
Pro It's free
Open source.
Pro Import/Export feature
Allows to share connections.
Pro Can open multiple sessions in different tabs
Pro Connection manager
Lets you organize your connections into folders with icons as well and allows nested folders as well.
Pro Supports multiple protocols
RDP (Remote Desktop/Terminal Server)
VNC (Virtual Network Computing)
ICA (Citrix Independent Computing Architecture)
SSH (Secure Shell)
Telnet (TELecommunication NETwork)
HTTP/HTTPS (Hypertext Transfer Protocol)
rlogin
Raw Socket Connections
Pro Inheritance from folder properties
Inheritance makes it possible to store properties on folder basis and let the underlying connections inherit this info.
Cons
Con Not a true terminal emulator
It's a PuTTY interface and it's mostly used to access remote machines through ssh, so it may not be very suitable for working on a local machine.
Con Private keys needs to be managed on PuTTY
Since mRemoteNG is integrated with PuTTY (included in the installation), all private key needs to be configured on PuTTY itself and then the PuTTY session needs to be selected on mRemoteNG.
