Connecting to a Windows PC using Remote Desktop Protocol (RDP) provides full graphical access for administration and troubleshooting without being physically at the machine.
The target PC runs the Remote Desktop host service, while the local PC uses Remote Desktop Connection (mstsc) to establish an encrypted session over the network, typically using TCP/UDP 3389 with Network Level Authentication (NLA) enabled.
The target PC must support hosting Remote Desktop (for example Windows 10 Pro, Windows 11 Pro, Enterprise, Education, or Windows Server) and must be reachable through firewall and routing rules. Directly exposing 3389 to the public internet increases attack surface; prefer a VPN or RD Gateway for off-site access.
Hosting Remote Desktop is not available on Windows Home editions.
Local Administrators are allowed by default; add non-admin accounts explicitly.
Limit the rule to Private or Domain profiles when possible.
ipconfig Ethernet adapter Ethernet: IPv4 Address. . . . . . . . . . . : 192.168.1.100 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1
Use the target PC name instead of an IP when name resolution is available.
Use a VPN when connecting from outside the local network.
Direct internet exposure of RDP is aggressively scanned and brute-forced; prefer a VPN or RD Gateway, or restrict inbound access to known source IPs.
PS C:\> Test-NetConnection -ComputerName 192.168.1.100 -Port 3389 ComputerName : 192.168.1.100 RemoteAddress : 192.168.1.100 RemotePort : 3389 InterfaceAlias : Ethernet SourceAddress : 192.168.1.50 TcpTestSucceeded : True
Use Windows + R to open Run quickly.
Use COMPUTERNAME\username for a local account, DOMAIN\username for a domain account, or the Microsoft account email address when applicable.
Only accept the prompt when the computer name or certificate thumbprint matches expectations.
Disconnect leaves programs running on the remote PC, while Sign out ends the session.