When comparing PuTTY vs mRemoteNG, the Slant community recommends PuTTY for most people. In the question“What are the best SSH clients for Windows?” PuTTY is ranked 2nd while mRemoteNG is ranked 20th.
Ranked in these QuestionsQuestion Ranking
Pro De facto standard client for SSH, Telnet and Rlogin
PuTTY is one of the oldest and most popular clients. It has earned the trust of a great number of users over a long period by being reliable, offering useful features and helpful support. It got into the 15 Essential Open Source Tools for Windows Admins list by InfoWorld.
Pro Source code available
Full source available. Compile and modify it yourself.
Pro Can be used on any Windows computer, even without admin rights
Pro Lightweight and portable
Doesn't require much resources (memory and hard-disk). Can even be run on a system by just downloading without install.
Pro It's free
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 Inheritance from folder properties
Inheritance makes it possible to store properties on folder basis and let the underlying connections inherit this info.
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)
Raw Socket Connections
Con Can not save passwords
Anyway, you can use "PuTTYgen" to generate a key pair, then use "Pageant" to do a password-less SSH remote login.
Con Ugly design, too simple
Looks very dated. Does the basic functions very well, but not much more.
Con Lacks features
It is JUST an SSH client. There are many other options with built in X-servers, Multitabbing, etc.
Con Tedious logging/tracing
Its tedious to set up logging and tracing (e.g. for serial connections).
Con No global settings
If you want to change a setting for all your connections, you'd have to do it individually.
Con No login scripting
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.