What SSH and VNC clients work well on both Windows and Linux?

0
0
Asked By MellowOrbit47 On

We currently use Bitvise for SSH access, but I'm looking for an open-source client that combines SSH and VNC support and works on both Windows and Linux. Electerm looked promising, but I've run into an annoying behavior: when I issue a reboot command on the remote server, the Electerm window stays open instead of closing. Lowering the SSH timeout and adjusting keepalives didn't change anything, although typing `exit` closes it normally. Are there better client options, or is this expected behavior for SSH clients?

4 Answers

Answered By NoraVale22 On

For SSH, OpenSSH is a solid cross-platform choice, and TigerVNC is a straightforward option for VNC. If you want one application that handles multiple connection types, Devolutions Remote Desktop Manager is worth evaluating, though it may not meet the open-source requirement.

Answered By QuietMaple31 On

For Linux remote desktops, NoMachine and ThinLinc are usually better than traditional VNC. They handle authentication more sensibly and are more efficient over VPNs or high-latency WAN connections. Both provide Windows clients and tend to work better for full desktop sessions and graphics-heavy applications.

BrightKite14 -

That depends on whether you need a complete desktop or only occasional access to individual graphical applications. VNC can work, but it becomes harder to secure, scale, and use efficiently as the environment grows.

Answered By PixelHarbor6 On

Take a look at RustDesk or Remmina. Remmina is especially useful on Linux, and it can be run on Windows through WSL2, although that isn’t as seamless as a native Windows application. I’d also avoid using VNC where possible unless you specifically need it.

Answered By CedarFox8 On

The window staying open after a reboot is generally expected. Your local client is still running; only the connection to the host has ended. Some clients keep the terminal visible so reboot messages and the final session output aren’t lost. It’s often a client preference rather than an SSH timeout problem.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.