Remote Desktop on Windows 11: Connect From Anywhere

Remote Desktop lets you control one Windows PC from another — full keyboard, mouse, and display access over the network or internet. You see the remote desktop as if you’re sitting in front of it, run applications, transfer files, and close your session when done without leaving any local trace on the connecting machine. For IT support, remote work, and accessing a powerful desktop from a laptop: it’s one of Windows’ most useful built-in features. We go deeper on the whole subject in our Complete Guide to Windows 11.

Two hardware requirements before anything else: Remote Desktop is only available to host on Windows 11 Pro, Enterprise, or Education. Windows 11 Home can connect to remote machines but can’t be connected to. If you want to remotely access a Home edition machine: third-party alternatives (Chrome Remote Desktop, TeamViewer, AnyDesk) work on Home.

Enabling Remote Desktop on the host machine

On the PC you want to access remotely (the host): Settings → System → Remote Desktop → toggle “Remote Desktop” On → “Confirm.” That’s the minimum required. Two important settings on the same page:

• Require devices to use Network Level Authentication (NLA): leave this On. NLA authenticates you before establishing the full remote session, which is more secure than the older method. Only very old Remote Desktop clients (pre-Windows Vista era) can’t use NLA; modern clients all support it.
• Remote Desktop port: default is 3389. Note this port number — it’s needed if you’re accessing from outside the local network and need to configure router port forwarding.

The host PC must be on and not asleep for the connection to work. Wake-on-LAN can wake a sleeping PC remotely if the network adapter supports it, but this requires additional configuration outside Remote Desktop itself.

Connecting to a Remote Desktop host

On the connecting machine: Win+S → “Remote Desktop Connection” → open the app → enter the host PC’s name or IP address → Connect → enter credentials (the host PC’s Microsoft account or local account username and password). The remote session opens in a window or fullscreen depending on your settings.

Finding the host’s name and IP address: on the host machine, Settings → System → About → “Device name” is the PC name (use this for connections within the same network). For IP address: Settings → Network & internet → click the active connection → the IPv4 address is listed. For connections within the same local network, either the PC name or local IP address works. For connections from outside the network (internet): you need the public IP of the network and router port forwarding.

Connecting over the internet

Connecting to a home or office PC from outside the local network requires either:

• Router port forwarding: forward external port 3389 (or any external port you choose) to the host PC’s local IP address on port 3389. Then connect using the network’s public IP address. Risk: exposing port 3389 to the internet attracts brute-force attacks — use a non-standard external port, a strong password, and ideally restrict which source IPs can connect.
• VPN: connect to a VPN that puts you on the same network as the host, then connect via local IP. More secure than open port forwarding; requires a VPN server (router-level VPN, or a hosted solution).
• Microsoft Remote Desktop with Azure AD / Entra ID: for Microsoft 365 Business and Enterprise users: the Remote Desktop app on non-domain devices can connect to Azure AD-joined machines through Microsoft’s infrastructure without port forwarding. Requires the right licences.

For home users who want simple internet remote access without VPN complexity: Chrome Remote Desktop (free, Google account, works on Windows Home) or AnyDesk are more straightforward than configuring router port forwarding.

For a wider look at the options here — including which are free, which handle file transfer, and which scale to multiple machines — see our roundup of the best remote desktop apps.

Remote Desktop configuration options

When connecting: the Remote Desktop Connection app has configuration options under “Show Options” before connecting:

• Display tab: resolution of the remote session and whether it uses multiple monitors. “Use all my monitors for the remote session” extends the remote desktop across all local monitors.
• Local Resources tab: controls which local resources (drives, clipboard, printers, audio) are shared with the remote session. Clipboard sharing lets you copy/paste between local and remote — extremely useful. Drive sharing makes local drives accessible from within the remote session (for file transfer).
• Experience tab: connection speed preset that adjusts visual effects. On slower connections: “Modem” preset disables wallpaper, animations, and fonts smoothing to improve responsiveness. On fast LAN connections: “LAN” preset enables all visual effects for full quality.

Save your settings: the “Save As” button in the app saves an .rdp file with all your configuration. Double-clicking the .rdp file in future connects with all saved settings without re-entering the host address and configuration each time.

Our guide on Windows 11 user accounts covers the account permissions required for Remote Desktop access, and our guide on Windows 11 network settings covers the firewall and network configuration that affects Remote Desktop connectivity. For enterprise Remote Desktop deployment including Remote Desktop Services (RDS), Microsoft’s Remote Desktop Services documentation covers the server-side infrastructure for managed multi-user remote desktop environments.

Firewall configuration for Remote Desktop

When you enable Remote Desktop in Settings: Windows automatically creates a firewall rule allowing Remote Desktop connections on port 3389 from the local network. If connections fail from within the same network: check Windows Defender Firewall: Control Panel → Windows Defender Firewall → Advanced settings → Inbound rules → “Remote Desktop” rule → ensure it’s enabled and the profile matches your network type (Private or Domain, not Public by default).

When that rule is missing, disabled, or overridden by another firewall, you get the familiar problem where Remote Desktop is not connecting on Windows 11 — walking through the full troubleshooting sequence is the fastest way to isolate which layer is at fault.

For allowing Remote Desktop connections from specific IP addresses only (more secure): Advanced firewall settings → right-click the Remote Desktop rule → Properties → Scope tab → “Remote IP address” → “These IP addresses” → add the allowed source IPs. This limits Remote Desktop access to specific machines rather than any device on the network.

Remote Desktop and multiple user accounts

By default: only the user accounts explicitly added to the Remote Desktop users list can connect. On the host: Settings → System → Remote Desktop → “Remote Desktop users” → add accounts. Members of the Administrators group automatically have remote access; standard users need to be added explicitly.

An important Remote Desktop behaviour: when you remotely connect to a PC while someone is locally logged in, you connect to their session (if it’s the same account) or they see a notification that another user wants to connect (if it’s a different account). If you take over their session: they’re logged out of the local display. The host PC can only have one active user session on the console at a time unless it’s running Remote Desktop Services (a server feature).

Remote Desktop’s main practical limitation is the Windows Home edition restriction. For Pro machines: it’s a powerful, zero-cost remote access tool that doesn’t require trusting a third-party service with your connection. For Home machines: the third-party tools fill the gap and are generally easy to set up, at the cost of routing your session through their servers rather than directly to your PC.

Remote Desktop app vs mstsc.exe

Windows 11 has two Remote Desktop clients: the classic “Remote Desktop Connection” (mstsc.exe) that’s been in Windows since XP, and the newer “Remote Desktop” app from the Microsoft Store. The classic mstsc.exe is accessible via Win+S and has the configuration options described above. The Microsoft Store app is designed for a more modern interface and has better support for Azure Virtual Desktop and Windows 365 scenarios.

For connecting to standard Windows PCs: mstsc.exe is sufficient and offers all needed features. The Microsoft Store app is worth trying for: Azure Virtual Desktop (cloud PCs), Windows 365 (Microsoft’s cloud PC service), or if you want a touch-friendly interface for tablet or convertible laptop use. Both work for standard Remote Desktop connections; the choice is mostly about interface preference.

Session disconnection vs sign-out

When you close the Remote Desktop window: by default, the remote session disconnects rather than signing out. The remote PC keeps running with your applications open — the session is “suspended” but not ended. The next time you connect: you resume exactly where you left off. This is the preferred behaviour for most remote work scenarios.

To end the session properly (sign out the remote user): in the remote session, go to Start → sign out, or from the Start menu → Power → Disconnect (which disconnects without signing out, keeping applications running) vs Sign out (which signs out and closes all applications). If you leave sessions disconnected indefinitely, applications on the remote machine continue consuming resources — RAM, CPU for background processes, network connections. Signing out periodically keeps the remote machine’s resource usage clean.

Performance optimisation for Remote Desktop

Remote Desktop responsiveness depends on: network bandwidth, network latency (ping), and the visual settings you’ve configured. A few settings that improve experience on constrained connections:

• Reduce colour depth: “Remote Desktop Connection” → Options → Display → Colors → 16-bit colour reduces bandwidth requirements significantly vs 32-bit, with minimal visual impact for most work
• Disable wallpaper: Options → Experience → uncheck “Desktop background” — a solid colour instead of a wallpaper eliminates unnecessary bitmap data
• Disable font smoothing and visual effects: Experience tab → same section — these settings affect aesthetics but transmit data for every rendered frame
• Enable RemoteFX compression: on modern hardware, RemoteFX uses GPU acceleration to compress the remote session stream more efficiently. This happens automatically if both client and host support it

Troubleshooting Remote Desktop connection failures

Common connection errors and their causes:

• “Remote Desktop can’t connect to the remote computer”: Remote Desktop not enabled on host, PC asleep, firewall blocking port 3389, wrong IP address or PC name
• “Credentials did not work”: wrong username format (use domainusername for domain accounts, or computernameusername for local accounts), wrong password, or account not in Remote Desktop users list
• “Remote session disconnected”: network interruption, idle session timeout (configured on host via Group Policy), or host PC restarted
• “An authentication error has occurred”: usually an NLA version mismatch. Check: the host requires NLA and the client version supports it. Also possible: CredSSP update required — search KB4093492 for the context if this is a recent Windows update-related error.

The most common single cause of Remote Desktop failures on home networks: the host PC is in sleep mode. Remote Desktop connections can’t wake a sleeping PC (unless Wake-on-LAN is configured separately). Power settings → Sleep → Never for a machine you want to be remotely accessible at all times. On laptops, “plugged in” sleep settings prevent sleeping when connected to power, which is appropriate for a machine used as a remote access host.

Remote Desktop for IT support

Remote Desktop is particularly useful for supporting other users’ machines remotely. The connection requires: the host user enabling Remote Desktop (needs Pro), adding the supporter’s account to Remote Desktop Users, and providing the PC name and IP address. Once connected: the supporter has full access to the remote desktop while the local user can watch and regain control at any time by moving the mouse or typing.

For supporting non-technical users who can’t configure Remote Desktop: Quick Assist (Win+S → “Quick Assist”) is a simpler alternative built into Windows 11. The helper generates a 6-character code; the user enters it on their machine; the connection is established through Microsoft’s servers without any firewall configuration. It’s session-based (not persistent like Remote Desktop) and designed specifically for support scenarios rather than regular remote work access. Related: Windows 11 File History.

Remote Desktop remains one of the most capable built-in remote access tools in any operating system. For Windows 11 Pro users who want reliable, direct, first-party remote access without subscription fees or third-party servers: configuring it properly and keeping the host machine awake and network-accessible provides a remote access solution that works indefinitely without any ongoing maintenance or cost. If this sounds familiar, Windows 11 Phone Link is worth a look.