Remote Desktop Protocol

Also known as: RDP · Remote Desktop · Remote Desktop Connection

On this page 7

Remote Desktop Protocol (RDP) is Microsoft’s proprietary protocol for presenting a remote Windows session on a local device, transmitting screen output to the client and keyboard, mouse and other input back to the host. In Windows administration it is the standard way to manage servers and workstations interactively without being physically present, and users usually meet it through the Remote Desktop Connection client.

RDP is more than screen sharing. It creates or attaches to a separate user session on the host, redirects local resources such as printers, drives and audio, and supports multiple concurrent sessions on Windows Server with Remote Desktop Services. Because it exposes a full interactive logon, it is also one of the most attacked services on the internet, so configuration and security matter as much as functionality.

How Remote Desktop Protocol transmits a session

RDP works by separating the session from the physical console. The host renders the desktop in a session managed by the Remote Desktop Services service, encodes the changing screen regions, and sends them to the client, while the client returns input events. By default the server listens on TCP port 3389, and modern versions also use UDP 3389 for a faster transport that tolerates packet loss.

Inside the connection, RDP multiplexes traffic into virtual channels. One channel carries graphics, others carry clipboard data, audio, drive redirection or smart card traffic. This design lets administrators disable individual channels through Group Policy, for example to block clipboard or drive redirection on sensitive servers.

ComponentRoleTypical setting
ListenerAccepts incoming connectionsTCP and UDP port 3389
Security layerEncrypts and authenticates the channelTLS with Network Level Authentication
Graphics pipelineEncodes screen updatesProgressive codec or H.264 encoding
Virtual channelsCarry clipboard, audio, drives and printersEnabled per policy
Session hostRuns the user’s desktop and applicationsOne session on client editions
Main components of an RDP connection

Authentication normally happens before the session is created through Network Level Authentication (NLA), which uses CredSSP to verify credentials first. NLA reduces the resources an unauthenticated attacker can consume and should remain enabled on every host.

Editions, licensing and session limits

Whether a Windows device can accept RDP connections depends on its edition. Every edition includes the client, but only business editions include the host component, and only Windows Server can host many simultaneous users with proper licensing.

Windows editionCan host RDPConcurrent sessions
Windows HomeNo, client onlyNot applicable
Windows Pro and EnterpriseYesOne interactive user at a time
Windows Enterprise multi-sessionYes, in Azure Virtual DesktopMultiple users
Windows Server, administrative modeYesTwo administrative sessions
Windows Server with RDS roleYesMany users with client access licenses

Windows Server allows two administrative connections without additional licenses. Running the Remote Desktop Session Host role for general users requires Remote Desktop Services client access licenses, assigned per user or per device, and a licensing server. Ignoring this distinction is a common compliance mistake in small environments.

Remote Desktop compared with other remote access methods

Remote Desktop is best for full interactive access to Windows, but it is not the only option and often not the best one for routine administration. Command-line and management tools consume fewer resources and expose a smaller attack surface.

MethodWhat it providesBest fit
Remote Desktop ProtocolFull graphical sessionInteractive administration and user desktops
PowerShell RemotingCommand-line management over WinRMScripting and bulk configuration
OpenSSH on WindowsEncrypted shell and file transferCross-platform command-line access
Remote Assistance and Quick AssistShared view of an existing sessionHelping a signed-in user
Microsoft IntunePolicy and application managementManaging devices without a session
VNC-based toolsMirror of the physical consoleNon-Windows hosts and console viewing
Choosing a remote access method

A key distinction is that RDP starts a separate session, while Quick Assist and VNC show the console session the user already sees. Connecting by RDP to a Pro workstation therefore locks out the local user, which surprises people who expect shared viewing.

Enabling and securing Remote Desktop

Remote Desktop is enabled in Windows Settings under System and Remote Desktop, through System Properties, or centrally through Group Policy. Enabling it opens the matching Windows Defender Firewall rule, and access is restricted to administrators and members of the Remote Desktop Users group.

The single most important rule is never exposing port 3389 directly to the internet. Automated scanners find open RDP listeners within hours and attempt password spraying, and unpatched hosts were vulnerable to wormable flaws such as BlueKeep. Remote access should pass through a Remote Desktop Gateway, a VPN or a zero-trust access service.

MeasureProtects againstHow to apply
Network Level AuthenticationUnauthenticated resource useRequire NLA on the host
Remote Desktop Gateway or VPNDirect internet exposurePublish only HTTPS through the gateway
Multifactor authenticationStolen or guessed passwordsUse Microsoft Entra ID or gateway MFA
Account lockout policyBrute-force attemptsSet thresholds in Group Policy
Restricted Admin or Remote Credential GuardCredential theft on the hostEnable for privileged accounts
Prompt patchingProtocol vulnerabilitiesApply monthly Windows updates
Recommended RDP hardening measures

Administrators should also review logon events in Event Viewer, where successful remote logons appear as event 4624 with logon type 10, and failed attempts appear as event 4625. A sudden burst of 4625 events is a reliable sign of an attack.

Limitations and common misconceptions

RDP performance depends heavily on latency more than bandwidth. Office work remains comfortable at round-trip times below about 100 ms, while graphics-heavy work degrades noticeably above that range even on fast links.

  • Changing the port from 3389 is obscurity, not security, and scanners still find it.
  • RDP encryption does not protect a host with weak passwords.
  • A Pro workstation does not support simultaneous users, and patches that unlock this violate licensing.
  • Disconnecting is not signing out; disconnected sessions keep running and hold resources.
  • Remote Desktop does not replace device management tools for fleets of computers.

Session time limits set through Group Policy help end abandoned sessions automatically, which frees memory on shared servers and closes sessions left open by departed users.

Understanding it simply

Remote Desktop Protocol lets a person use a Windows computer from somewhere else as if sitting in front of it. The distant computer does the work, and a picture of its screen travels over the network to the person’s own screen. Every keystroke and mouse movement travels back the other way.

It is a little like a long cable for the monitor, keyboard and mouse, except the cable is the internet or the office network. Because anyone who reaches that cable could try to log in, it has to be protected with strong passwords and kept behind secure entry points.

Applied in practice

A systems administrator at a regional logistics company manages twelve Windows servers in a data center two hours away. Port 3389 is closed on the external firewall. Instead, the company publishes a Remote Desktop Gateway over HTTPS that requires multifactor authentication through Microsoft Entra ID.

When a scheduling application stops responding at 6 a.m., the administrator connects from home through the gateway, opens an RDP session to the application server, and finds a stuck Windows service in the Services console. Restarting it takes four minutes, and no one has to drive to the site.

A weekly review of Event Viewer shows only expected logon type 10 events from the gateway address. Over the same period, the firewall logs thousands of blocked scans against port 3389, confirming that keeping RDP off the internet stopped the attacks before they reached any server.