Anyone who administers more than a couple of servers knows the window sprawl: an RDP session here, two SSH terminals there, a VNC console forgotten behind the browser. mRemoteNG ends the sprawl by putting every remote connection into one tabbed window. It is a free, open-source connection manager for Windows that speaks RDP, SSH, VNC, Telnet and several other protocols, organises your machines in a folder tree, and stores credentials securely so a whole environment opens with a few clicks. This guide explains how it works and how to set it up well.
What Is mRemoteNG?
mRemoteNG is the actively maintained fork of the classic mRemote application. It acts as a universal remote-connections hub: instead of a different client per protocol, you define each server once — its address, protocol, port and login — and open it in a tab inside the main window, next to every other session. An SSH terminal can sit beside an RDP desktop and a web-based admin page, all reachable from one tree.
Connections are stored in a configuration file (optionally encrypted and protected by a master password, or kept in a SQL database for teams), with folders, inheritance and search. Inheritance is the feature administrators fall in love with: set a domain, gateway or credential once on a folder, and every connection inside it inherits those values until you override them.
Supported Protocols
The built-in list covers the protocols working administrators actually use: RDP (with Remote Desktop Gateway support), SSH-1 and SSH-2 through an embedded PuTTY engine, Telnet, VNC, ICA/Citrix, HTTP/HTTPS pages rendered in tabs, rlogin, RAW, and external applications for anything unusual. Because SSH runs through PuTTY, saved PuTTY sessions and settings carry over, and features like port forwarding are available from the same configuration.
Key Features
Day to day, the wins are organisational. The connection tree groups servers by client, site or function; a quick-connect bar opens an ad-hoc session by typing an address; screenshots, external tools and custom commands can be attached to connections — for example, opening a server's monitoring page or file share with one right-click. Sessions can be reconnected in bulk, so after a reboot or VPN drop, your whole working set returns with one action.
Security is taken seriously for a free tool: the configuration can be encrypted with AES using your master password, credentials are not stored in plain text, and a portable edition exists for administrators who carry their toolkit on a USB drive between sites.
Getting Started
Install mRemoteNG, create a connection file, and add your first server: right-click to add a connection, enter its hostname, choose the protocol, and fill in the credentials — or leave them blank to be prompted. Then organise: create folders for environments (Production, Staging, Clients), set shared values on the folders, and watch individual connections shrink to just a name and an address. Within an hour, most administrators have their entire estate in the tree and their old pile of shortcuts deleted.
Frequently Asked Questions
Is mRemoteNG free? Yes — free and open source, for personal and commercial use.
Does it run on macOS or Linux? It is a Windows application. Mac and Linux administrators usually run it in a Windows VM, or use native alternatives, while managing the same servers through the same protocols.
Can a team share one configuration? Yes. The configuration can live in a SQL Server database with per-user views, or a shared encrypted file — both common in small IT teams.
Conclusion
Remote administration is not hard because the protocols are hard; it is hard because there are so many windows. mRemoteNG's tabbed, tree-organised, protocol-everything approach removes that friction for free. Set it up once, inherit your settings sensibly, and your whole server estate becomes one window away. The downloads and documentation are at mremoteng.com.
