how to

Set Up Remote Desktop on Windows 11 the Right Way

· 3 min read windows-11remote-desktopnetworkingrdp

Windows 11 Pro, Enterprise, and Education include a full RDP host, letting you control the machine from another PC, a Mac, or a phone as if you were sitting in front of it. Home edition lacks the host component but can still act as the client. Setup takes minutes; doing the security steps at the end is what separates a convenient tool from an exposed attack surface.

What you need

  • Windows 11 Pro, Enterprise, or Education on the machine being controlled
  • A user account with a non-empty password (RDP rejects blank passwords)
  • The client device and both machines on the same network, or a VPN/tunnel for remote access

Step by step

  1. On the host, open Settings > System > Remote Desktop and toggle it On. Confirm the UAC-style prompt.
  2. Keep Network Level Authentication enabled in the same panel; it requires identity verification before a session is established and blocks most automated attacks.
  3. Note the PC name shown on that page. If you prefer connecting by address, run ipconfig in Terminal and record the IPv4 address.
  4. Decide who may connect. By default your own account works. To add others, open System Properties (sysdm.cpl > Remote tab > Select Users) and add standard accounts; they will need to type COMPUTERNAME\username at login.
  5. Confirm the firewall allows it: enabling Remote Desktop via Settings creates the needed rules automatically, but verify in Windows Defender Firewall > Allow an app through firewall that Remote Desktop is checked for Private networks.
  6. Set a static-ish address so reconnecting is easy: reserve the host's IP in your router's DHCP settings, or set a static IP in Settings > Network > the adapter's IP assignment edit screen.
  7. From the client, open the Remote Desktop app (mstsc.exe on Windows, Microsoft Remote Desktop elsewhere), enter the PC name or IP, supply credentials, and accept the certificate warning the first time.
  8. Harden for internet exposure. Never port-forward 3389 raw through your router. Instead use a VPN into your home network, or tunnel with ssh -L 3390:localhost:3389 user@your-gateway and point the client at localhost:3390.

For quick ad-hoc help sessions between two machines you control, Quick Assist (built into Windows 11) avoids configuration entirely, though it is assistance-oriented rather than full unattended access.

Common mistakes

  • Exposing RDP directly to the internet, which bots scan constantly
  • Leaving NLA disabled for compatibility with ancient clients
  • Trying to RDP from Home edition as the host and wondering why the toggle is absent
  • Connecting with a Microsoft account email but not knowing the password; local sign-in credentials are what the prompt wants

Related guides

If the host also runs Linux in [[dual-boot-windows-11-linux]], remember only one OS can serve RDP at a time. Tune session performance with [[power-plan-tuning-windows-11]], keep the host lean using [[windows-11-debloat-startup-apps]], and know [[reset-windows-11-without-losing-files]] if remote troubleshooting hits a wall.

← All guides