X2Go Alternative: When SSH Port 22 Is the Wall
X2Go has one trick that most remote desktop tools still cannot match: you close the client, go home, open it on another laptop, and the session is exactly where you left it.
Blog
Tips, guides, and news about remote access — from the team building Tenvo.

X2Go has one trick that most remote desktop tools still cannot match: you close the client, go home, open it on another laptop, and the session is exactly where you left it.

Remmina is the client most Linux desktops reach for first. On Ubuntu it is already installed, it opens RDP, VNC, SPICE and SSH sessions from one window, and it costs nothing.

If your fleet runs on TeamViewer and you need to migrate—because of cost, licence headaches, or vendor risk—your top priority should be: never leave a machine unreachable.

You found AGPL code that looks useful, but you’re not sure what it means for running it inside your company. The common anxiety is practical: will you be forced to publish private code, expose internal systems, or open a legal minefield if you modify the software and use it behind your firewall?

You're in a remote support session and need to move a file — fast and safely. Remote desktop file transfer looks simple until you hit a size limit, a permission error, or a corporate firewall.

Port forwarding used to be the simple answer: punch a hole in the home router, map TCP 3389 or a custom port, and you could reach the machine from anywhere. Today many of those machines are unreachable because the carrier puts customers behind CGNAT.

If you try to control a remote machine over satellite internet you already know the pain: long, variable round‑trips and occasional packet loss turn a smooth remote‑control session into a laggy, jumpy mess.

You want unattended remote access to a PC running Windows 11 Home and you keep running into walls: mstsc can connect out but not in, domain tools aren’t available, and online guides promise hacks that break after updates.

You’re measured on first call resolution and every metric point feels like survival. The pressure leads teams to add more steps, longer notes, and busywork that looks productive but doesn’t fix users.

You know the feeling: a ticket opens, you schedule a remote session, and somewhere between the ticket and the control session the clock eats an hour.

You need a clear, defensible policy for recording remote support sessions: engineers want evidence to troubleshoot and investigate, compliance teams want auditability, and users want their privacy preserved.

Getting a "commercial use suspected" notice from TeamViewer feels like a slap you didn't see coming. You installed it to help your parents or remote into your home PC, and suddenly sessions are limited or blocked.

You want to run a full-screen game or a GPU-heavy video remotely — but you also need to edit code, read PDFs, or click tiny UI controls. Which technology actually fits each task?

You spend more time repeating the same remote fixes than doing anything that moves your org forward: password resets, disk cleanups, patching, and chasing down low-disk alerts at 02:00.

People click "Approve" for a living. If your ai approval workflow looks, feels and times out exactly like every other prompt, you get reflex clicks — not real decisions.

You already trust remote desktop tools for support, administration and remote work. The new wrinkle: an AI agent — a script-and-model combo — will sometimes operate the remote machine without a human at the keyboard.

You need short, practical answers — not marketing — when a remote session fails, a compliance auditor asks, or you’re deciding between a self-hosted tunnel and a managed relay.

You need to get remote access working reliably and securely—fast. This guide gives a practical, 30-minute overview: what matters, which architecture to pick, a quick setup checklist, security caveats you must know, and where to study deeper.

Corporate firewalls block remote desktop sessions in ways that feel arbitrary: UDP dropped, outbound ports restricted, mandatory HTTP proxies, and enterprise TLS inspection.

You need to connect to a remote machine from a coffee shop, airport, or hotel and you know public Wi‑Fi is sketchy. This guide walks through the exact threats you face, what protections actually work (and their limits), and a tight, actionable checklist you can run before, during and after a session.

Trying to connect to a remote machine from inside China and watching every tool fail is a familiar, infuriating problem. This guide explains why connections break, which approaches actually work behind the Great Firewall (GFW), and practical configuration and testing steps you can use today.

You need to know how much data a remote session really uses — not marketing numbers, but a repeatable calculation you can apply to staffing, billing, or hosting decisions.

You're trying to budget for remote support and remote access, and the price quotes on vendor sites don't tell the full story. Monthly subscription numbers look small until you add management, Windows licensing, self-hosted servers, or the extra staff time needed to keep a self-hosted stack running.

You're buying remote-access software and hate vague marketing claims. You need a practical, repeatable way to compare tools on the things that actually matter: security, latency, manageability, and cost.
Download Tenvo for free and connect to your devices in under a minute.