Windows 11 RDP vs RustDesk vs Chrome Remote Desktop: Best Secure Option for Slow Internet

In a hands-on evaluation published by MakeUseOf, IT specialist Gregory Gibson put three of the most widely discussed free remote access options—Google’s Chrome Remote Desktop, the open-source darling RustDesk, and Microsoft’s built-in Windows Remote Desktop Protocol (RDP) routed over Tailscale—through an intentionally unforgiving real-world gauntlet. Rather than relying on a cozy local area network, Gibson spun up a disposable Windows 11 Pro virtual machine on a Proxmox server at home, tethered a Windows 11 Home laptop to a rural mobile data connection, and physically walked outside to catch a signal.

The resulting cellular link offered a nominal 10 Mbps symmetrical throughput crippled by an upload latency exceeding 600 milliseconds—and those Speedtest numbers represented best-case bursts rather than sustained bandwidth. Behind a home internet connection locked down by Carrier-Grade NAT (CGNAT), each contender had to prove it could deliver readable text, responsive window management, reliable clipboard syncing, User Account Control (UAC) administrator elevation, unattended recovery after a system reboot, an 80 MB file upload, and usable smartphone controls.

The outcome wasn't even close. While third-party relay tools have their place for quick-and-dirty support, Microsoft’s venerable Remote Desktop Protocol—paired with a private Tailscale subnet gateway—delivered the fastest file transfers, the sharpest visual fidelity, and the most responsive mobile experience. Here is a deep dive into how all three architectures performed under high-latency pressure, why protocol design dictates real-world usability, and how to configure a secure remote Windows 11 setup without exposing your PC to the public internet.

The Rural Cellular Torture Test: Why Latency Breaks Remote Desktops​

To understand why these three tools behaved so differently in Gibson’s testing, it helps to look at what happens under the hood of a remote session. When you control a Windows 11 PC from afar, the software isn't just sending a passive video stream like Netflix; it is running a tight, interactive feedback loop. Every mouse movement, keystroke, and window drag must travel up your connection, register on the host operating system, and return a visual update before your brain notices the delay.

When upload latency spikes above 600 ms on a rural cellular tether, chatty protocols and heavy full-frame encoders choke. In MakeUseOf’s test bed, the three tools relied on two fundamentally different networking philosophies:

• Public Relay Infrastructure: Both Chrome Remote Desktop and RustDesk were tested using their default public infrastructure. Because the home network sat behind CGNAT—meaning the ISP does not assign a directly routable public IPv4 address to the home router—connections had to be brokered or relayed through external servers managed by Google and RustDesk.
• Private Mesh Overlay (Tailscale): Windows RDP is a direct peer-to-peer protocol that does not operate a public cloud relay for consumer PCs. To punch through the CGNAT barrier safely, Gibson routed RDP traffic through an existing Tailscale subnet router running on his home network, creating a private encrypted tunnel straight to the Windows 11 Pro virtual machine.

Summary: Under a high-latency 10 Mbps mobile link, protocol efficiency and routing paths separated usable desktop workflows from frustrating slideshows.

Chrome Remote Desktop: Convenient in a Pinch, Blurry Under Pressure​

Google’s Chrome Remote Desktop is often the first tool users reach for because it is free, cross-platform, and runs directly inside a web browser. According to Google’s official Chrome Help documentation, the service supports Windows, macOS, and Linux hosts, secures sessions with full encryption, and gates unattended access behind a user-defined PIN tied to a Google account.

In MakeUseOf’s rural mobile test, however, that browser-centric convenience came with steep performance and workflow trade-offs:

• The Account Trade-Off: Setting up unattended access requires signing into the same Google account on both ends. While Google accounts support two-factor authentication (2FA) and require at least a six-digit PIN to initiate a session, tying full administrative control of a desktop PC to a ubiquitous consumer web account is a philosophical non-starter for many security-conscious administrators.
• The Blur-Versus-Lag Dilemma: Connecting to the Windows 11 VM from Firefox on the tethered laptop yielded a noticeably soft, blurry desktop image alongside perceptible input lag when typing or dragging windows. Enabling Chrome Remote Desktop’s High-DPI mode sharpened the text considerably, but the extra pixel load overwhelmed the 600 ms mobile connection, introducing severe lag that made actual work frustrating. Turning off smooth scaling offered only minor relief, forcing a choice between legible text and usable frame rates.
• Browser Clipboard Friction: Because Gibson connected via Firefox rather than a Chromium browser, clipboard synchronization wasn't seamless out of the box; it required toggling synchronization on and installing a dedicated Firefox add-on. Even after setup, copying and pasting text suffered from heavy lag.
• Painfully Slow File Transfers: Uploading an 80 MB test file through Chrome Remote Desktop’s browser upload/download drawer took roughly 8 minutes—nearly eight times slower than Windows RDP over the exact same cellular connection.
• Mobile Usability: Accessing the host via a smartphone browser required switching from direct touch (which turned tapping tiny Windows icons into a guessing game) to trackpad mode, which proved much more accurate.

To its credit, Chrome Remote Desktop handled administrative elevation—displaying the Windows UAC prompt when launching an elevated PowerShell window—and successfully reconnected after the VM was restarted.

Summary: Chrome Remote Desktop remains a viable backup for quick emergency tweaks when all you have is a browser, but its soft image scaling, sluggish file transfers, and high-DPI lag make it poorly suited for full-time remote work over weak connections.

RustDesk: Crisp Open-Source Performance Held Back by Public Relay Limits​

For users fleeing commercial tools like TeamViewer or AnyDesk—which frequently nag free users with commercial-use suspicions—RustDesk has emerged as the premier open-source alternative. According to RustDesk’s official documentation, the client runs across Windows, macOS, Linux, Android, iOS (as a controller, as iOS devices cannot be remotely controlled), and the web, offering end-to-end encryption and a built-in file manager.

When Gibson tested RustDesk over his rural mobile link using RustDesk’s free public servers, the session was a tale of two extremes:

1. The 40-Second Handshake​

Initiating the connection took between 30 and 40 seconds—a delay long enough to convince most users that the session had timed out and failed. Once the handshake finally cleared the public relay, however, RustDesk’s performance blew past Chrome Remote Desktop. The Windows 11 desktop rendered sharply, window animations moved smoothly, clipboard redirection was instantaneous, and the 80 MB file transfer finished in a respectable 1 minute and 48 seconds using the built-in file transfer tool. Admin elevation via UAC and unattended access after a reboot (configured via a permanent password) worked without a hitch.

2. Why RustDesk’s Public Server Now Demands a Login​

During testing, Gibson noted that using RustDesk’s public relay now requires signing in through a third-party identity provider such as Google, GitHub, or Microsoft. Crucially, this login does not authenticate your device connection itself; rather, it is an anti-abuse gate.

According to a July 2026 security briefing from the RustDesk Team, the project implemented mandatory controller logins on its public servers—and previously withdrew its official listing from the Google Play Store in September 2023—to combat rampant tech-support scammers and botnet abuse. Scammers routinely trick victims into installing remote access tools, and anonymous public relays made automated ID enumeration and scam operations trivial. RustDesk’s documentation explicitly states that its public servers are operated for demonstration and testing rather than production or sensitive workloads.

3. Mobile Quirks and the Self-Hosting Imperative​

On a smartphone, RustDesk’s mobile client offered both a virtual trackpad and a direct touch mode. In Gibson’s testing, touch mode rendered an oversized cursor graphic that sent the pointer flying across the screen whenever a fingertip four times wider than a desktop icon tried to click a target.

If you plan to adopt RustDesk for serious Windows administration, industry best practices and RustDesk’s own documentation point toward self-hosting your own hbbs (ID/rendezvous) and hbbr (relay) services. Furthermore, if you configure unattended access on a RustDesk host, RustDesk’s security documentation recommends three essential hardening steps:

1. Set a unique permanent password that is never reused on your Windows OS account or email.
2. Enable TOTP Two-Factor Authentication (2FA) on the controlled device (Settings > Security), requiring a live six-digit authenticator code alongside the password before any unattended session is authorized.
3. Configure IP Whitelisting (Settings > Security > Use IP Whitelisting) when connecting from predictable VPN or office CIDR ranges.

Summary: RustDesk delivers sharp visuals, fast clipboard syncing, and brisk file transfers, but its free public relays suffer from slow initial handshakes and are meant only for testing. It shines brightest when paired with a self-hosted relay server.

Windows RDP Over Tailscale: Why the Old Standby Won the Crown​

There is a reason enterprise system administrators have relied on Microsoft’s Remote Desktop Protocol for decades. Unlike screen-scraping tools that merely capture, compress, and transmit raw framebuffer video, RDP is deeply integrated into the Windows graphics subsystem, intelligently translating display primitives, fonts, and input events.

In Gibson’s rural mobile test, connecting to the Windows 11 Pro VM via RDP over a private Tailscale gateway delivered an immediate, unmistakable upgrade:

• Near-Local Responsiveness: Sessions connected rapidly and delivered crisp, native text clarity that felt nearly indistinguishable from sitting at the Proxmox console.
• Blistering File Transfers: Simply copying and pasting the 80 MB test file directly between the local and remote File Explorer windows completed in 1 minute and 3 seconds—beating RustDesk by 45 seconds and Chrome Remote Desktop by nearly seven minutes.
• The Drive Redirection Trap: While manual copy-and-paste flew, Gibson uncovered a critical real-world caveat for high-latency users: RDP Drive Redirection. Enabling drive redirection mounts your client laptop’s entire local storage inside the remote PC’s File Explorer. While convenient on a fast local network, enumerating a redirected drive over a 600 ms cellular connection choked File Explorer so severely that Gibson had to forcibly terminate the RDP session just to regain control.
• A First-Class Mobile Experience: On Android, Microsoft’s unified Windows App (which replaced the legacy Remote Desktop client across Windows, macOS, iOS, iPadOS, Android, ChromeOS, and web browsers) proved vastly superior to both rivals. It dynamically refitted the Windows 11 desktop whether the phone was held in portrait or landscape orientation, provided smooth touch and trackpad controls, and exposed granular device redirection toggles for the phone’s camera, microphone, storage, clipboard, and location—capabilities verified by Microsoft Learn’s Windows App documentation.

Summary: When shielded behind a private VPN tunnel, native Windows RDP remains unmatched in visual sharpness, input responsiveness, file copy speed, and mobile ergonomics—provided you keep full drive redirection turned off on slow connections.

The Catch: Edition Limits and the Golden Rule of RDP Security​

Before you ditch your third-party remote tools for Windows RDP, two non-negotiable architectural requirements stand in the way:

1. The Windows 11 Pro Host Requirement​

As confirmed by Microsoft Support’s official Remote Desktop documentation, while any edition of Windows (including Windows 11 Home) can act as an RDP client to initiate outgoing connections, the remote PC hosting incoming connections must run Windows 11 Pro (or Enterprise/Education). Microsoft blocks incoming RDP hosting on Windows 11 Home.

2. Never Expose Port 3389 to the Public Internet​

Windows RDP has a notorious reputation in cybersecurity circles for one simple reason: users forward TCP/UDP port 3389 on their home routers directly to the public internet. Automated botnets scan the entire IPv4 space around the clock looking for exposed RDP ports to subject to credential stuffing and brute-force attacks. Even Microsoft Learn’s official documentation on allowing outside access warns against opening your PC directly to the internet, explicitly recommending a Virtual Private Network (VPN) instead.

Keeping Network Level Authentication (NLA) enabled—as Gibson did in his test—forces a connecting user to authenticate before Windows spins up a full graphical session, which helps defend against denial-of-service resource exhaustion and unauthenticated login-screen exploits. However, NLA is not a substitute for network isolation.

How to Replicate This Setup Safely with Tailscale​

In Gibson’s test, the secret weapon was Tailscale, a zero-config mesh VPN built on the WireGuard protocol. Because his home network already ran a Tailscale subnet router (a gateway device configured with tailscale set --advertise-routes=<subnet> to bridge an entire local LAN into a private tailnet), his laptop and Android phone could reach the Windows 11 Pro VM’s private IP address from anywhere in the world without opening a single port on his home router and despite his ISP’s CGNAT.

Notably, Tailscale’s official subnet router documentation points out that while a subnet router is ideal for appliances or virtual lab environments where you don't want to install agents everywhere, single-PC users have an even simpler path: installing the Tailscale client directly on both the host Windows 11 Pro PC and the client laptop or phone. Direct installation requires zero subnet-routing math, traverses CGNAT automatically, and establishes direct end-to-end encrypted WireGuard tunnels between your devices.

To set up a bulletproof remote Windows 11 Pro workstation today:

1. Verify Your Host Edition: On your target PC, navigate to Start > Settings > System > About and confirm your edition is Windows 11 Pro.
2. Enable Remote Desktop with NLA: Go to Start > Settings > System > Remote Desktop, toggle Remote Desktop to On, and ensure the option requiring devices to use Network Level Authentication is checked.
3. Deploy Your Private Overlay: Install Tailscale (or a self-hosted WireGuard VPN) on both your host PC and your remote laptop/phone, or configure a local Tailscale subnet router if you manage multiple homelab subnets. Do not forward port 3389 on your router.
4. Optimize for Cellular Links: When connecting from the Remote Desktop Connection app (mstsc.exe) or the cross-platform Windows App over mobile data, leave full local Drives redirection unchecked under Local Resources. Stick to standard clipboard copy-and-paste inside File Explorer to prevent directory enumeration from locking up your session.

The Verdict: Choosing the Right Tool for Your PC​

Gibson’s real-world field test strips away marketing hype and highlights a classic IT truth: native protocols almost always outperform wrapper tools when paired with proper networking.

If your target machine runs Windows 11 Home and you refuse to pay for a Pro upgrade or tinker with network tunnels, Chrome Remote Desktop works as an occasional lifeline, and RustDesk gives you a crisp, responsive desktop—especially if you graduate from its slow public relays to a cheap self-hosted server.

However, if you are running Windows 11 Pro, the combination of native Windows RDP and Tailscale is in a league of its own. It bypasses CGNAT without router port forwarding, keeps your attack surface hidden from public scanners, transfers files in a fraction of the time, and turns even an Android phone over a 600 ms rural cell tower into a genuinely usable Windows workstation.