"We can't choose the music that life gives us, but we can choose how to dance to it."
*****@*****
OS: Ubuntu MATE 24.04.3 LTS x86_64
Host: 10FLS3DV00 ThinkCentre M900
Kernel: 6.14.0-37-generic
Uptime: 4 days, 19 hours, 5 min
Packages: 2552 (dpkg), 9 (snap)
Shell: bash 5.2.21
Resolution: 1920x1080
DE: MATE 1.26.1
WM: Metacity (Marco)
Theme: Yaru-bark-dark [GTK2/3]
Icons: Yaru-bark-dark [GTK2/3]
Terminal: mate-terminal
Terminal Font: Monospace 8
CPU: Intel i5-6500T (4) @ 3.100GHz
GPU: Intel HD Graphics 530
Memory: 6891MiB / 7832MiB
Somewhat new to Linux and I’m trying to figure out how to set up my desktop for remote access. I want to be able to access it while I’m away from the house from my laptop. I’ve tried a couple of techniques I’ve read about on the internet, but it seems I’m getting nowhere.
I use a VPN. Do I need to disable that? Are there any settings I am overlooking here that would prevent my laptop from being able to access this desktop?
Thanks,
DM
2 Likes
Have you changed your sharing preferences on your desktop ?
Have you tried Remmina ?
If you don’t have Remmina on your Ubuntu installation, install it with sudo apt install remmina remmina-plugin-vnc. You can also use snap package (sudo snap install remmina).
By the way… I do like your reference to Life’s music 
W
2 Likes
I do much the same thing, but using xrdp (which uses Microsoft's Remote Desktop Protocol) ( sudo apt install xrdp). I use Macs primarily as guest machines, so I use a Parallels Client for Mac (there are free versions for all popular OSes). I also use Microsoft's Remote Desktop at times. All that is necessary to do on the Linux side is enable the port you want to use (3389 is the default) through the firewall. You can easily do this via
sudo ufw allow 3389 -- use another port if you wish; make sure your client uses it, too.
An alternative I've found handy at times is NoMachine. This is a free client-server system that uses its own protocol and port setup. On your Linux server, download and install the software (https://www.nomachine.com/) and configure it as needed. Then start the server. On your client, download the software and point it to your Linux machine. Again, you'll need to open a firewall port, as above.
In my experience, NoMachine has a bit more reliability, but is a bit slower from the other side of the world (yes, I've done that). I've had instances where xrdp goes wonky, but if I can ssh to my server, I can reset it. A hassle, but when I need to connect from anywhere on the globe, the hassle is worth it!
2 Likes
Use Remmina, or xrdp, or even dockerized Apache Guacamole (the last one is tough to set up the first time). I’ve use all three methods as well as using shellinabox as a local-only fallback (really should just use SSH as the fallback). The advice the others have given are good but avoid NoMachine or TeamViewer stuff. They come knocking at random times with license threats.
You can pipe your machines through your VPN (OpenVPN for me) if you wish but adds complexity but it can be done if you have a decent router that exposes some sane configuration options.
One thing I found required once you get all connected is to always lock the remote desktop; if the session isn’t locked you’ll end up with a black screen with cursor bug the next time you remote in again without recourse other than to reboot it…somehow.
1 Like
I have never had NoMachine make any noise about licensing. I didn't care for TeamViewer's look and feel, so I don't ever use it.
1 Like
TeamViewer was the culprit in our case, used ad hoc in an corporate environment by shadow-ops from an engineering department. Triggered an audit for IT once number of seats reached their install trigger. Used NoMachine many, many years ago and only for a very brief time.