Remote Desktop Services Runs On Which Port?

9 Answers 9

Remote Desktop requires TCP port 3389 to be open up. Also, opening UDP port 3389 enables dispatch since RDP eight.0.

Information technology is possible to change the port used by the terminal server (or PC which is accessed), see this Microsoft support article: How to change the listening port for Remote Desktop. The UDP port for accelerated connexion uses the aforementioned port number as the TCP setting and cannot be changed separately.

UDP acceleration is available since RDP eight.0 (shipped with Windows 8 and Windows Server 2012, available via an update on Windows 7 / Windows Server 2008 R2).

You lot tin can likewise take a dissimilar port if you use port forwarding. The private port is 3389 as said to a higher place unless y'all change it, and the public port tin can be any. I accept mine set to 10000, so when I connect using Remote Desktop Connection, I have to enter mycomputer.com:10000

May 25, 2009 at eighteen:47
Updated link to MS support article: support.microsoft.com/en-u.s./assist/306759. For reference, the registry cardinal is HKEY_LOCAL_MACHINE\Organisation\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber.

Oct 29, 2018 at 18:04
@MarkBerry It says RDP tcp... should i not block 3389 on udp?

Jul 5, 2019 at 10:22
@deadManN - Most firewalls and routers block all inbound ports unless yous open up them, so if y'all have that equally a default dominion, for RDP, you simply need to add an exception for TCP 3389.

Jul vi, 2019 at 15:28
Notation that RDP, especially on the default port 3389, is increasingly a target for hacking, e.g. past GoldBrute. Also, there have been ii RDP vulnerabilities disclosed in the concluding two months: CVE-2019-0708 and CVE-2019-9510. Patch, don't apply RDP, or utilise 2FA for RDP.

Jul 6, 2019 at xv:47

In addition to opening port 3389 for UDP and TCP, I had to get edit the windows firewall rule and set Edge traversal to allow. Like this:

enter image description here

Which version of Windows is this and how did you go there?

Dec ix, 2018 at 18:30
@BrianZ This is Windows 7/8/10 and to go there, but open up Outset Card search for "Firewall" and click on "Avant-garde Settings" on the left-side panel, click on Inbound Rules on left-side panel and on the main panel find Remote Desktop - User Mode (TCP-In) and Remote Desktop - User Mode (UDP-In) and Let border traversal for both of them.

Jan iii, 2019 at xix:xv
It works for me without this setthing, why do you sparse this is necessary?

Mar 12, 2019 at 11:02

If you don't want to use 3389 externally, open a different port externally, simply point it to 3389 on the IP address of the car you want RDC on. This is helpful for routing many systems with RDC. Information technology's also dainty because it won't require any registry edits.

This should be the accepted answer. You should never annunciate 3389, and y'all will demand a different port for each instance behind NAT anyway.

April ten at 21:32

The only exception to the previous answer (3389) is when using Pocket-size Business Server through Remote Web Workplace.

In this case the server NAT'due south the connexion between you and server port 80 (HTTP) or 443 (HTTPS), and then to the internal computer; then only eighty/443 is required.

What ports should I open up for remote desktop - Answer: None.
Opening RDC to the Internet is a BAD IDEA. Port scanners will pick upward an open 3389 pretty apace and try to break your logon. https://www.grc.com/port_3389.htm

Fair enough, but opening the port to a specific IP accost is non bad practice at all.OP did non specify that opening to the general public was the intention.

Feb 7, 2018 at 17:04
This should rather be a comment than an answer.

Jan 31 at 6:05

If security is concerned and you happen to have an Linux based router(e.k. OpenWrt), and so don't add together whatsoever NAT entry, for 3389 in this example.

Use your router as a jump server and create a SSH port forward.

Your router'due south sshd listens on 22 port for LAN network.
it also listens on port A for WAN network(the only ane exposed), with just public-key authentication, so no brute force password attempts.
create public/private central pair, put the private 1 on your client devices, re-create the public one onto your router (into the authorized_keys file)
establish the tunnel from your client devices: ssh -p [port A] -Fifty:[port B]:RDP-box:3389 root@router (you can relieve this in SSH config or Terminal profiles for ease use in the future)
connect RDP from localhost:[port B]

we can set custom RDP port numbers using following path >> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Command\Terminal Server\WinStations\RDP-Tcp

Non the answer yous're looking for? Browse other questions tagged remote-desktop rdp windows port or ask your own question.