mRemoteNG
An open-source Windows connection manager for RDP, VNC, SSH, Telnet, HTTP/HTTPS, rlogin, raw sockets, PowerShell Remoting and external tools in tabbed sessions.
What mRemoteNG does
mRemoteNG organizes RDP, SSH, VNC, Telnet, HTTP/HTTPS, rlogin, raw-socket and PowerShell Remoting sessions in a tabbed tree. Inheritance, SFTP and external tools reduce repeated connection work, while the same central configuration can concentrate host details and credentials.
Release status and migration
1.78.2 NB 3405 is a preview package with a self-contained build and a newer .NET runtime line. The older 1.76.20 stable release is from 2019 and uses older dependencies. Keep the two installations separate, test configuration conversion on a sanitized copy and retain a verified rollback path.
Protocols and connection files
RDP, SSH, VNC, Telnet and raw sockets have different authentication and encryption properties. XML, CSV, database files, logs and external-tool arguments may contain infrastructure details or credentials. Use a strong master password, minimize exports and avoid putting secrets in command-line arguments.
Maintenance note
This page reviews mRemoteNG 1.78.2 NB 3405, the 1.76.20 line, Windows support, connection migration, protocol boundaries and GPL-2.0 licensing. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave mRemoteNG to this cloud drive
Baidu Netdisk
Save mRemoteNG to this cloud drive
mRemoteNG 1.78.2 NB 3405 isolated testing and migration guide
Keep the preview build in a separate directory, create a sanitized connection copy, test RDP and SSH first, and migrate only after encryption, export and rollback behavior are confirmed.
Before you start
- Use a supported Windows device and prepare an isolated test account, snapshot or rollback environment; keep the old installation untouched.
- Copy existing connection files and settings, then remove passwords, private hostnames and customer data before importing the test copy.
- Use permission-limited RDP, SSH or VNC targets; test Telnet, rlogin and raw sockets only inside a controlled network.
Installation steps
- 01
Extract the preview package separately
Scan the archive, review its file list and extract it outside the stable installation and production configuration directory.
- 02
Create a blank protected profile
Start with a new test configuration, set an independent strong master password, close and reopen the application, and verify that save and restore work.
- 03
Import a minimal sanitized copy
Import only a few non-production connections and check protocol, port, inheritance, external tools and credential sources individually.
Quick start
- 01
Test RDP and SSH
Connect with an ordinary account, review RDP certificate or SSH host-key prompts and keep server identity checks enabled.
- 02
Review inheritance and protocol properties
Inspect inherited usernames, gateways, resolutions and credential fields so moving a connection does not add a production secret unexpectedly.
- 03
Verify export and rollback
Export a minimal XML copy, close and reopen it, then retain an old read-only backup until the new profile has passed connection and recovery checks.
Usage tips
- A preview label calls for compatibility and security testing; a higher version number is not a reason to skip rollback planning.
- Prefer SSH, SFTP, modern RDP or a controlled tunnel over legacy Telnet, rlogin and unencrypted socket workflows.
- External tools can expand host, username and password variables. Passing a password on the command line may expose it through process lists or logs.
Troubleshooting and uninstall
Why does the preview build not open an old connection file?
Work on a copy, check the master password, XML integrity and logs, and export a smaller connection set from the old installation rather than overwriting the original.
Why does an RDP, SSH or VNC session fail?
Verify the server and network with an independent client, then check the protocol component, certificate, host key, gateway and inherited properties before changing algorithms.
- Revoke test credentialsSave a sanitized recoverable connection list, remove test keys, accounts and tokens that are no longer needed, and clear external-tool arguments that expand secrets.
- Remove the preview dataEnd all sessions, delete the preview directory and review local application data, logs, XML files, PuTTYNG sessions and caches before removing anything that is the only backup.
Frequently asked questions
Is mRemoteNG 1.78.2 NB 3405 a stable release?
It is marked as an early preview package. Test configuration compatibility, password protection and rollback before considering it for production use.
Why not simply use the older stable 1.76.20 build?
That line dates from 2019 and uses older dependencies. Its stable label does not represent current security coverage, so evaluate isolation and replacement options separately.
Can I send an mRemoteNG connection file to a colleague?
Export only a minimized, sanitized copy through a controlled channel, set a strong master password and remove host details and credentials that the recipient does not need.