What is Reddit's opinion of mRemoteNG?

From 3.5 billion Reddit comments

Haven't tried the others recommended, but I got introduced to MRemoteNG, and have been using it since. can organize folders of connections into dev, qa, staging, prod, (just what I do), and between applications, etc. like a file system of organization for connections. Only used it in Windows, so can't comment in Linux/Unix experiences.

https://mremoteng.org

P. S. Not a shill at all.

If I have to use Windows, then my first go-to tool is mRemoteNG. This is a fantastic "wrapper" for PuTTY, the main selling point (it's free!) over plain PuTTY is the profile management. Basically, you can store your connections in a hierarchy and keep the common settings at the top level, such as passwords if you store them, but other things too like connection type. This means that if you have a large amount of servers you connect to, then you only need to keep one set of credentials/preferences, which makes maintenance much easier. mRemoteNG also supports other connection protocols, such as VNC, RDP, etc.

Another tool I will use frequently is Termius. The attraction for this terminal emulator is that it is available across most platforms (Linux, Windows, macOS, Android, iOS), and so offers a familiar interface across all the platforms I use. It also looks really nice too, which is ok I suppose. Termius is a commercial offering, but is perfectly usable on a no-cost subscription, you just lose some of the higher-end features, but it has enough to make it very usable. I personally think they set the price for the personal subscription too high, otherwise I would buy it.

mRemoteNG is my daily RDP/SSH client. I save the confcons.xml file to my Dropbox folder and I can then open it on all my systems when I need to. Also has the ability that when a new person starts on my team, I can export the file to them and remove all saved passwords. Great tool!

What is this, the 1990's?

But really, you could just look for an SSH connection manager. I know that mRemoteNG has a "PuTTY Saved Sessions" section. So just create a telnet session in PuTTY, save it, and it will show up in mRemoteNG. Unless you have to use tekterm for some reason, then I'm not sure.

Use mremoteng or Microsofts Remote Desktop Connection Manager to run the RDP sessions. They can both handle the scaling in any setting you prefer.

You could try https://mremoteng.org/ which is freeware. As far as I know, there was mRemote, which was freeware, but developer stopped working on it to develop Royal TS (shareware). mRemote was ported and it is still developed as mRemoteNG.

I am using Royal TSX on Mac and it is really good, so I think you should try both, maybe the freeware one is good enough, but Royal TS is not very expensive, so it might be worth getting a license for that.

You will not loose access to your VM by enabling HTTPS on your Apache webserver.

SSH runs on port 22, while HTTP runs on port 80 and HTTPS runs on port 443. Due to this, a HTTP(s) server on you VM won't interfere with the SSH daemon listening on port 22.

You're also safe on that, if you somehow configured Apache to run on port 22, it would fail to start as the port is in use by SSHD. It should be noted that if you had Apache running on port 80 and you configured and restarted SSHD to run on port 80 you'd loose access to your VM as SSHD would fail to start.

As to alternatives to SSH, I'm not sure. I will say that some form of SSH server is installed by default on the vast majority of Linux distros, it may not be running by default but it will be started. There are a variety of SSH clients though (the most popular GUI version being puTTY), I've been using mremoteNG recently which is pretty good.

mRemoteNG might do it for you. I'd suggest PAC, but I don't think they have a Windows port.

SecureCRT is a paid application, and is very popular with Windows users. RDP management is hacky, but supposedly works. You can get a trial from VanDyke Software.

We're already using mRemoteNG as a single interface for all of our RDP sessions to servers and SSH sessions for network gear, Linux servers, etc..

I guess it can't hurt to have the option to connect to Windows PC's with SSH, but we've been using PowerShell remoting (Enter-PSSession) for a while now. Can't think of a compelling reason to stop using PS remote sessions in lieu of SSH.

I really like mRemoteNG. It uses PuTTY, but gives you tabs, saved configurations, organization, and allows you a command center not just for SSH but for RDP and other protocols.

Could you elaborate on what you want specifically for UX?

I just found RDCMan and started setting it up but I may have to give https://mremoteng.org/ a try now after seeing it in this thread. Being able to connect to RDP, VNC, SSH, Telnet, HTTP/HTTPS, rlogin, Raw soctes and PowerShell remoting all in one tool is definitely enticing.

Your post is a bit unclear, but if you mean that you want to have a list of servers that you can save and easily connect to them from, you might want to have a look at RDCman, https://docs.microsoft.com/en-us/sysinternals/downloads/rdcman. It's a program by the Windows sysinternals team at Microsoft that is used to connect to remote computers over RDP and it's very handy. I think t RDCman only supports windows though, so if you have a mixed platform environment, mRemoteNG ( https://mremoteng.org/ ) might be another option that support more connection protocols.

I use mRemoteNG, and that can run Windows exe's against the IP addresses of existing SSH sessions as an external tool.

https://mremoteng.readthedocs.io/en/latest/user_interface/external_tools.html

I guess it depends whether Winbox can take command line arguments for the address.

I use mRemoteNG (https://mremoteng.org/), which has been a lovely change of pace after too many years putting up with RDCMan.

It has options for importing from AD, by port-scan or from a file. It's free, open-source and pretty spiffy. It doesn't have central management but you can export your current setup to file. It supports using Powershell to generate XML files for connection management (see https://mremoteng.readthedocs.io/en/latest/howtos/bulk_connections.html), so maybe you could use Github/Subversion/ect for tracking updates to the connection profiles.

Hyper-V is a good and obvious way to start since you are running Windows 10 and have it already on board, you don't have to install anything.

Since you have mentioned fast switching I would avoid using built-in Hyper-V Console since it's pretty sluggish. Depending on what kind of OS you are running inside your virtual machines I would recommend using some kind of RDP (Windows) or VNC (Linux) manager that allows multiple open sessions. This way you switch just the tabs within the same application and the experience is very similar to what you have with VMware Fusion.

You can start with mRemoteNG which is opensource and supports RDP and VNC along with SSH/Telnet and some others.

https://mremoteng.org/

I ran across mRemoteNG, while it's traditionally a RDP session manager I found that it can be set to launch a traditional vsphere client for earlier ESX hosts, as well as a browser session for 6.5 +

and still have the ability to create folders and directory structure.

It's not perfect but far better that an excel sheet.

Thanks to all that replied with suggestion.

sauce https://mremoteng.org/

For your local machine mRemoteNG

You can create a local db for everyone or depts or w/e. Uses putty for ssh

I prefer superputty for ssh

If you're looking for 3rd party, you could use jumpoints for rdp and ssh with Bomgar

RD Tabs is good, but I've introduced a number of places to mRemoteNG which I like the interface for a lot better, especially on widescreen monitors. It can also handle displaying multiple simultaneous connections, but in my particular use case the screen resolution often prevents multiple RDP connections from being that useful since the text gets too small to really see. YMMV on that one.

It also has its own subreddit at /r/mRemoteNG

Mremote - der einzige grund weswegen ich noch produktiv auf windows bin. Ein wunderbarer rdp client inclusive ssh v1 und v2. Speichert Verbindungen in einer exportierbaren .xml und unterstützt credential-based login, für leute, die zu faul sind ihre passwlrter ständig einzutragen.

mRemoteNG lets you save SSH, RDP, VNC, and a bunch of other formats I don't use and don't remember. You can organize them so that everything in a folder uses the same username and/or password so you don't have to type it in for everything.

https://mremoteng.org/

does ssh and windows, lets you catagories and organise all the logins.

​

for the rest just search for a bash cheatsheet, their are plenty

If you have a decent number of devices I highly suggest looking into either Devolutions RDM, RoyalTS, or mRemoteNG. All of them combine RDP, SSH, VNC, and (especially in the case of the first two) a TON of other management tools into one cross-platform app with methods to maintain lists of devices, integration with credential managers, and so on.

If you don't opt for one of the above, some good direct replacements would be:

>Termius (SSH) - JuiceSSH
>
>RD Client (remote desktop) - This exists on Android
>
>NZBget client - Probably exists on Android, but try NZBUnity
>
>Tautulli remote - This exists on Android
>
>OpenVPN - This exists on Android
>
>Home Assistant (this one is important for me) - I run HS3, so I've never tried it, but take a look at HomeAssist.
>
>IFTTT - This exists on Android
>
>Stringify - This exists on Android

Will the server be local to the client or are we talking "over the Internet" type remote-access? For local servers with a Windows 10 client I use mRemoteNG and VNC or SSH on the Linux Server (usually both), RDP on Windows Servers, and VNC for headless Macs (need a video dongle for that).

For "over the Internet" remote access, I use a free personal license of Teamviewer 13 (if you do not have control of firewall ports) or nomachine.com if you do control the firewall.

...and if you don't want to spend money on something like this, you can try mRemoteNG ( https://mremoteng.org/ , https://github.com/mRemoteNG/mRemoteNG ). It's free and it's released under an opensource license.

I discovered mRemoteNG a while back a love it. It handles the scaling issue, plus lets you aggregate all types of connections into a single console (RDP, telnet, VNC, etc.).