Port 3389 — Windows Remote Desktop

TCP/UDPRemote Management

Windows Remote Desktop defaults to 3389. Check the TCP and UDP paths used by your deployment and whether Remote Desktop is enabled.

Registry assignments, software defaults and local listeners are different things. A port number alone does not identify or secure a service.

Configuration and troubleshooting

Microsoft documents PortNumber, matching firewall rules and client testing. Arrange console or recovery access before changing a remotely managed endpoint.

Important limitations

Avoid opening RDP to the entire internet for convenience. A different port does not strengthen authentication; use controlled network access and policy.

Read-only checks: run on the server host

Choose the commands for your OS. Check TCP and UDP separately. No result is not a lasting availability guarantee; inspect host and container separately.

Linux

sudo ss -ltnp 'sport = :3389'
sudo ss -lunp 'sport = :3389'

macOS

sudo lsof -nP -iTCP:3389 -sTCP:LISTEN
sudo lsof -nP -iUDP:3389

Windows PowerShell

Get-NetTCPConnection -LocalPort 3389 -State Listen
Get-NetUDPEndpoint -LocalPort 3389

Sources and review

Sources checked on: 2026-09-05

This review covers the explanations and sources on this page, not your device or every community software entry below.

Microsoft — change RDP listening port

Related troubleshooting guides

Windows: find a port’s owner and resolve conflicts safely

Software Using This Port (3 software)

Community software entries: links are references, not individual verification.

Microsoft Terminal Services

WindowsRemoteDesktopService

FreeRDP

RDPClient

Reference link ↗

Remote Desktop Protocol

MicrosoftRemoteDesktopProtocol(RDP)

Usage Suggestions

Before using port 3389, please confirm it is not occupied by other services
If you encounter port conflicts, consider using other ports or stopping the occupying service