What the Remote Desktop Protocol is
The Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft that enables a user to connect to another computer over a network and interact with its graphical desktop. The remote computer runs the applications and renders the desktop; the local device — your PC, Mac, phone, or tablet — displays the picture and sends back keyboard, mouse, and touch input.
RDP is built on a family of ITU-T standards (the T.120 series) originally designed for multi-channel conferencing, extended by Microsoft with virtual channels that carry everything beyond the basic screen-and-input stream: clipboard data, audio, printers, drives, smart cards, and more. That extensibility is why a modern RDP session feels like sitting at the machine rather than peering at it through a keyhole.
A brief history
RDP's lineage goes back to the 1990s. Microsoft introduced terminal-services-style remote access with Windows NT 4.0 Terminal Server Edition (1998), and RDP became the built-in remote administration story for Windows 2000 Server and Windows XP. Each Windows era brought a new protocol generation — RDP 5.x, 6.x, 7, 8/8.1, and 10 — adding better compression, richer graphics remoting (RemoteFX), UDP transport for smoother performance, and stronger encryption.
Today RDP is woven into the Windows ecosystem: every Windows Server and Pro edition can host sessions, Windows includes the mstsc client, and Microsoft ships free Remote Desktop clients for macOS, iOS, and Android. Decades of iteration are why RDP remains the default remote-desktop choice in Windows environments.
How a session works
A Remote Desktop Protocol session follows a clear sequence:
- Connection. The client opens a TCP connection to the server's RDP port — 3389 by default — and the two sides negotiate capabilities and protocol version.
- Security handshake. Modern sessions upgrade to TLS encryption, and Network Level Authentication (NLA) verifies your credentials before the server spends resources building you a session.
- Logon. You authenticate with a username and password (and any additional factors the server requires).
- Session. The server renders its desktop, compresses the screen updates, and streams them to you; your input, clipboard, audio, and redirected devices flow back through virtual channels.
Because the server sends only what changes on screen — using caching and compression — RDP stays usable on modest bandwidth. UDP transport in newer versions further smooths the experience on lossy networks by carrying time-sensitive graphics data without TCP's retransmission delays.
Headline features
RDP is more than screen sharing. Its virtual-channel architecture enables:
- Clipboard redirection — copy text or files on one side, paste on the other.
- Drive redirection — your local drives appear inside the remote session for easy file transfer.
- Printer redirection — print from remote apps to your local printer.
- Audio redirection — hear the remote machine's sound locally, or use your mic remotely.
- Multi-monitor support — span the remote desktop across your local displays.
- Smart card and device redirection — use local security keys and peripherals inside the session.
These redirections are per-session settings — an administrator can enable or restrict each one, which matters for both convenience and security policy.
RDP vs alternative protocols
| Protocol | Origin | Strengths | Typical use |
|---|---|---|---|
| RDP | Microsoft (proprietary) | Deep Windows integration, rich redirection, efficient compression | Windows servers and desktops |
| VNC | Open (RFB protocol) | Cross-platform, simple | Mixed-OS environments, lightweight needs |
| SSH + X11 | Open | Secure, scriptable | Linux administration |
| PCoIP / Blast | Teradici / VMware | High-end graphics remoting | Virtual desktops, CAD, media |
For Windows workloads, RDP's integration — single sign-on, Group Policy control, native clients on every major platform — usually makes it the pragmatic choice. Alternatives shine where RDP doesn't reach, like headless Linux administration.
Security basics
RDP's security story has two halves: the protocol's and yours. The protocol side is solid in modern versions — TLS encryption and Network Level Authentication are standard. Your side is where breaches happen, and it's almost always one of these:
- Weak passwords. Automated bots constantly probe port 3389; a strong, unique password defeats them.
- Unpatched servers. Keep Windows updated — protocol vulnerabilities get patched, but only help if installed.
- Open to the world. Restrict RDP access by IP allowlist, VPN, or an RD Gateway instead of exposing 3389 to the entire internet.
- No lockout policy. Account lockout after failed attempts blunts brute-force attacks.
Handled well, RDP is a secure, mature remote-access standard — which is exactly why it still underpins everything from enterprise VDI to the rented RDP servers buyers use every day. For port-level specifics, see our guides to the RDP port and port 3389.
Ready for your own RDP server?
Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan. Pay by credit/debit card, bank transfer, Bitcoin or altcoins.
3-day money-back guarantee · Instant setup · 30+ server locations · 99% uptime SLA
Remote Desktop Protocol: FAQ
The Remote Desktop Protocol (RDP) is Microsoft's proprietary protocol for connecting to another computer over a network and using its graphical desktop remotely. The remote machine runs the software; your device displays the screen and sends keyboard and mouse input.
Microsoft developed RDP, building on ITU-T T.120 conferencing standards. It debuted with Windows NT 4.0 Terminal Server Edition in the late 1990s and has been refined through many versions since.
RDP uses port 3389 by default — TCP traditionally, with UDP added in newer versions for smoother graphics. Administrators often change or restrict it for security.
Modern RDP uses TLS encryption and Network Level Authentication, which is solid. Most real-world breaches come from weak passwords, unpatched servers, or exposing port 3389 to the whole internet — all fixable with basic hardening.
RDP is Microsoft's Windows-integrated protocol with rich features like clipboard, audio, and printer redirection plus efficient compression. VNC is an open, cross-platform protocol that's simpler but generally less efficient and less Windows-integrated.
The server side is Windows, but clients exist for every major platform — Windows includes mstsc built in, and Microsoft provides free Remote Desktop apps for macOS, iOS, and Android.
