Port3389— Windows Remote Desktop
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:3389Windows PowerShell
Get-NetTCPConnection -LocalPort 3389 -State Listen
Get-NetUDPEndpoint -LocalPort 3389Sources and review
Sources checked on:
This review covers the explanations and sources on this page, not your device or every community software entry below.
Related troubleshooting guides
Software Using This Port (3 software)
Community software entries: links are references, not individual verification.
Microsoft Terminal Services
WindowsRemoteDesktopService
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
Frequently asked questions
What is port 3389 used for?
Port 3389 sits in the Remote Management category. This page lists the registered purpose and the software commonly associated with it; to see what is actually listening on a specific machine, check the process with ss/netstat.
Is port 3389 TCP or UDP?
The registered protocol on this page is TCP / UDP. The same number behaves independently on each protocol: TCP may be listening while UDP is idle, so check them separately.
How do I check if port 3389 is in use?
On Linux: sudo ss -tlnp 'sport = :3389' for an exact port match. On macOS: sudo lsof -nP -iTCP:3389 -sTCP:LISTEN. On Windows PowerShell: Get-NetTCPConnection -LocalPort 3389 -State Listen. A listener counts as confirmed only when you can see the bind address and process name; without root/admin you will not see other users' processes.
Is port 3389 secure? Should I open it in my firewall?
A port number has no inherent security — it depends on whether the listening service is correctly configured and whether it needs exposure at all. Keep loopback/internal-only services firewalled; where public access is required, pair it with source restrictions, VPN or authentication. The caution section on this page lists port-specific risks.
Quick Info
- Port
- 3389
- Protocol
- TCP/UDP
- Categories
- Remote Management
- Usage Status
- 3 software in use
Related Ports
Need Help?
If you find incorrect information or need to add more, please submit correction information.
Submit Correction