A community dedicated to the profession of IT Systems Administration
We make the prompt be user@hostname so no matter what you use it shows what host you're on. This is configurable in .bashrc iirc.
I might also recommend tmux, there's a script you can use to also set prompt in the window view. Though this is best used as a jumpserver setup.
mRemoteNG has always been my go-to. Supports multiple remote protocols, though I've typically only used it for SSH and RDP. Tabbed interface, save a list of endpoints with the connections configs, etc. SSH just runs an instance of putty within the program, so it's pretty straightforward.
Mobaxterm has many more features than what you’re asking for. You might not use anything else after using it.
Agreed here.
Have you tried putty?
Two ways come to mind.
One is tmux. The other is editing your .bashrc (I'm assuming your shell is bash, adjust accordingly if it's a different shell) to have relevant info in your prompt (common is username@hostname).
Oh. also Windows Temrinal supports themes, and you can configure different commands to run when opening a given shell.
You definitely should put username@hostname in your prompt. This has saved me from so many mistakes. And if your shell supports it use red if the user is root.
Bull blown client... mobaxterm.
Or just use screen and a custom screenrc config to name your tabs.
Setting the terminal title is done through a standard escape sequence: https://unix.stackexchange.com/a/177598
If it's not working, make sure your terminal emulator is set to something like xferm, and that your console host program recognizes this sequence (which Konsole and Windows Terminal should).
Take a look at Remmina. Modular and can be used for ssh, rdp and vnc.
I believe with tmux, you should be able to do that, and even set up an automatic session with 3 ssh connects with named already configured. Hope that helps!
I’d recommend the free edition of Remote Desktop Manager by Devolutions. It’s way more features than your current use case so it definitely as the room to grow if you want to expand the connection types you are using.
It will do connection and credential management, our primary use is for RDP but also use it for web sessions and SSH.
We use RoyalTS and I've been very happy with it. I've used mRemoteNG and Mobaxterm in the past, and there really isn't much that would have me switch back. Plus, it supports plenty of other protocols besides SSH, so more of our teams can leverage it.
This tool I just found out about the other day and it’s still early in development but has some awesome features and some huge time savers built into it!