📡 Network Administration — Interactive Lesson

Remote Desktop Protocol

A comprehensive exploration of RDP — from OSI layer mapping to packet structure, security vulnerabilities, and hands-on header construction.

TCP/3389Default Port
7 LayersOSI Mapping
TLS 1.3Encryption
CredSSPAuth Protocol
01

Protocol Overview

🖥️ What is RDP?

Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft that provides a user with a graphical interface to connect to another computer over a network connection. It transmits the display output from the remote computer and sends keyboard/mouse input from the client.

RDP operates primarily on TCP port 3389 (and optionally UDP 3389 for enhanced performance) and supports features like clipboard sharing, file transfer, audio redirection, and multi-monitor support.

📅 History & Evolution

  • 1998 RDP 4.0 introduced with Windows NT 4.0 Terminal Server Edition
  • 2002 RDP 5.2 — Windows Server 2003, introduced NLA precursors
  • 2008 RDP 6.1 — Remote Apps, NLA, CredSSP introduced
  • 2012 RDP 8.0 — RemoteFX vGPU, adaptive graphics
  • 2022+ RDP 10.x — TLS 1.3, improved compression, Azure Virtual Desktop

🔑 Key Features

Graphical remote access • Clipboard sync • File transfer • Audio/video redirection • Printer redirection • Smart card auth • Multi-monitor • RemoteApp

⚙️ Core Components

RDP Client (mstsc.exe) • Remote Desktop Services (RDS) • Connection Broker • Session Host • Virtual Channel Manager • MCS Transport Layer

📋 Admin Skills Required

Port configuration & firewall rules • NLA enforcement • Group Policy for RDP • Certificate management • Network Level Authentication • Session monitoring

📊 Port Reference Table

PortProtocolServiceDescriptionStatus
3389TCPRDPPrimary remote desktop connection✅ Required
3389UDPRDPEnhanced performance, optional⚪ Optional
443TCPRD GatewayHTTPS tunneling of RDP traffic🔒 Secure
3391UDPRD GatewayUDP transport for RD Gateway⚪ Optional
3388TCPLegacy RDPOlder alternate port (deprecated)⚠️ Legacy
02

RDP & the OSI Model

RDP operates across multiple OSI layers. Click each layer to explore how RDP interacts with it.

👆 Select a Layer

Click any OSI layer on the left to see how RDP interacts with it and what concepts network administrators must understand.
03

Protocol Architecture & Packet Flow

🏗️ RDP Protocol Stack

RDP Application Data (Graphics, Input, Audio)
Virtual Channel Manager
MCS (Multipoint Communication Service)
T.125 / T.123 Transport
TLS / CredSSP Security Layer
TCP (Port 3389)
Physical / Data Link

🤝 Connection Sequence

Click a step above to see details.

📺 Virtual Channels

RDP multiplexes multiple data streams over a single connection using Virtual Channels (VCs). Each channel handles a specific type of data.

rdpdr
Drive, printer, port, and smart card redirection
cliprdr
Clipboard synchronization between client and server
rdpsnd
Audio output redirection to the client device
drdynvc
Dynamic virtual channels — USB, camera, multimedia
MS_T120
Core graphics and input channel (always present)
echo
Latency measurement / keep-alive channel
04

RDP Header Builder

Construct an RDP protocol data unit interactively. Adjust the fields below and watch the packet visualization update in real time.

🔧 RDP PDU Constructor

📦 PACKET VISUALIZATION (click a byte for details)

Click "Build Packet" to generate visualization
Click any byte in the packet visualization to see detailed field information.
Hex Representation
-- Build packet to see hex --
Protocol Analysis
-- Build packet to see analysis --
05

Security, Threats & Hardening

Critical

🔴 BlueKeep (CVE-2019-0708)

Pre-authentication RCE vulnerability affecting Windows XP through Server 2008 R2. Allows unauthenticated attackers to execute code. Wormable — no user interaction required. Patched May 2019 — systems must be updated.

Critical

🔴 DejaBlue (CVE-2019-1181/1182)

Similar pre-auth RCE vulnerabilities affecting Windows 7–10 and Server 2008–2019. Part of the same BlueKeep family. Heap-based buffer overflow in RDP decompression routines.

High

🟠 Brute Force / Credential Stuffing

RDP exposed on port 3389 is a prime target for automated brute-force attacks. Attackers use tools like Hydra, Crowbar. Account lockout policies and NLA significantly mitigate this risk.

High

🟠 Man-in-the-Middle (MITM)

Without proper certificate validation, RDP sessions can be intercepted. Self-signed certificates accepted by default. Enforce TLS with validated certificates to prevent credential interception.

Medium

🔵 Pass-the-Hash Attacks

NTLM credentials captured from one system can be replayed to authenticate RDP sessions on other hosts. Restricted Admin Mode and Protected Users group mitigate this attack vector.

🛡️ Hardening Checklist

🔐 Authentication Methods

Network Level Authentication (NLA) — Authenticates the user before a full RDP session is established. Uses CredSSP (TLS + NTLM/Kerberos). ✅ Recommended
Smart Card Authentication — Certificate-based auth using PKI. Eliminates password brute-force risk. Requires smart card infrastructure deployment.
Multi-Factor Authentication — Azure AD Conditional Access, Duo Security, or RADIUS integration with TOTP adds a second factor to RDP logins.
Classic RDP Authentication — Password only, no pre-auth. ⚠️ Avoid in production
06

Glossary of Key Terms

07

Knowledge Check

0/10
Correct Answers