The built-in Remote Desktop (based on the RDP protocol) is the most stable, smoothest, and completely free way to connect two fixed Windows machines. How is it different from ToDesk, Sunflower, or TeamViewer, how do you enable it, and what do you do when it will not connect? All covered here.

How RDP differs from remote control software

Set the positioning first:

  • RDP is native, free, smooth, and light. By default it works best on the same LAN; cross-network needs a tunnel. Only one person can operate at a time and it locks the other screen. Windows 11 Home cannot be remote-controlled (no allow switch).
  • ToDesk, Sunflower, and TeamViewer work across networks immediately, can control a phone, and support unattended access, but the free tier is throttled or ad-supported.

In short, use RDP for an office LAN or two home PCs; use ToDesk or Sunflower to help parents remotely or to control a PC from a phone.

Enable Remote Desktop on Pro or Enterprise

  1. Settings > System > Remote Desktop, turn on the switch (it confirms and adds a firewall exception automatically).
  2. Or in sysdm.cpl, the Remote tab, check Allow remote connections to this computer (keep Allow connections only from computers running Network Level Authentication).
  3. The controlled account must have a password (passwordless accounts cannot RDP in; set a password or switch to a local account, see Switch a Microsoft Account to a Local Account).

What if Home has no allow remote switch

Windows 11 Home cannot be a host by default (it can be the client but not the controlled end). Three options:

  1. Upgrade to Pro. Settings > System > Activation > upgrade, the cleanest and legal path.
  2. Use a third-party tool. ToDesk, Sunflower, or Quick Assist (Microsoft's built-in, the controlled side must accept, good for temporary help).
  3. RDP Wrapper, a third-party patch that enables the RDP server on Home. It modifies system components and carries compatibility, security, and compliance risk, and Microsoft updates often revert it. Not recommended for non-technical users.

How to connect (client side)

  1. Press Win + R, type mstsc, and press Enter to open Remote Desktop Connection, or install Windows App or Remote Desktop from the Microsoft Store.
  2. In Computer, enter the target's LAN IP or hostname (same network); for cross-network enter the public IP or the tunneled address.
  3. Enter the target's username and password and connect. On first connect it asks whether to trust the certificate; check Don't ask again and confirm.
  4. To find the target IP, on the target run ipconfig and read IPv4; for the hostname run hostname. For network discovery or sharing see Windows File and Printer Sharing on a Local Network.

Eight reasons it will not connect, and fixes

Symptom or errorMost likely causeFix
Computer not found or timeoutTarget off, not on same network, wrong IPConfirm target is on and pingable; use the correct LAN IP
Remote Desktop not enabledTarget switch is offEnable it in section two
Credentials do not work, repeated promptsPasswordless account, wrong username, Microsoft account needs emailSet a password; use email or hostname\username
Cannot connect to the remote computerFirewall blocks 3389, network profile is PublicAllow Remote Desktop in target firewall; set network to Private
NLA required but client does not support itNewer builds force Network Level AuthenticationUpgrade client; or temporarily relax NLA on target
0xC000000DTarget has admin protection on, non-admin RDP failsTemporarily turn off admin protection or wait for Microsoft
Remote Desktop Services not runningService disabledservices.msc, enable and start the service
Black screen or dropGPU driver or resolution negotiationUpdate driver, lower remote resolution

Cross-network access, safety first

Do not map port 3389 directly to the public internet; that is a prime target for brute force. Recommendations:

  • Build a virtual LAN with a tunnel such as Tailscale, ZeroTier, or Dandelion, then run RDP inside the virtual network, far safer than exposing 3389.
  • Keep a strong password and Network Level Authentication (NLA) on.
  • You can change the default port in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp, PortNumber, but do not rely on port change as security.
  • For long-term exposure use a VPN or zero-trust solution; do not use a personal free channel for sensitive operations.

Redirecting audio, printers, and drives

During a remote session you are not limited to the screen. In the Remote Desktop client, under Show options > Local Resources, you can bring your local printers, clipboard, and even a mapped disk into the remote machine, which is handy for moving files without email. For audio, the client can play remote sound locally so a video on the host is heard on your end. Performance also depends on resolution and color depth; dropping to 1080p and 16-bit color on a weak connection keeps it responsive, and redirecting a large local drive over a slow link is slow, so copy what you need rather than mounting the whole disk.

Using Remote Desktop from a phone or a Mac

You are not limited to a Windows client. Microsoft ships a free Remote Desktop app for macOS, iPhone, iPad, and Android, so you can reach your home or office PC from virtually any device. The setup is the same: enable RDP on the host, then in the app add the PC by its LAN IP or tunneled address and sign in with your account. On a phone the small screen means you should pick a lower resolution and rely on the on-screen trackpad; on a Mac the experience is close to native. The same security rules apply, so keep it inside a tunnel rather than opening 3389 to the internet.

Summary

RDP is Windows built-in free high-performance remote access. Pro enables it in Settings with one switch; Home either upgrades or uses ToDesk, Sunflower, or Quick Assist. For connection failures, check the table top to bottom (switch, network, firewall, credentials, NLA, service). Never expose 3389 directly across the network; use a tunnel.