Port3389— Windows Remote Desktop
Windows Remote Desktop utilise 3389 par défaut. Vérifiez les chemins TCP et UDP utilisés par votre déploiement et l’activation de Remote Desktop.
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 documente PortNumber, les règles de pare-feu correspondantes et les tests côté client. Prévoyez un accès console ou de récupération avant de modifier un point de connexion administré à distance.
Important limitations
Évitez d’ouvrir RDP à tout Internet par commodité. Un autre port ne renforce pas l’authentification ; encadrez l’accès réseau par des contrôles et des politiques.
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
Logiciels utilisant ce port (3 logiciels)
Community software entries: links are references, not individual verification.
Microsoft Terminal Services
WindowsRemoteDesktopService
Remote Desktop Protocol
MicrosoftRemoteDesktopProtocol(RDP)
Conseils d’utilisation
- Avant d’utiliser le port 3389, vérifiez qu’il n’est pas occupé par d’autres services
- En cas de conflit de ports, envisagez d’utiliser d’autres ports ou d’arrêter le service qui occupe le port
Questions fréquentes
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.
En bref
- Port
- 3389
- Protocole
- TCP/UDP
- Catégories
- Administration à distance
- État d’utilisation
- 3 logiciels utilisant ce port
Ports associés
Besoin d’aide ?
Si vous trouvez des informations incorrectes ou souhaitez en ajouter, veuillez proposer une correction.
Proposer une correction