Announcement

Collapse
No announcement yet.

How to change the RDP listening port for Remote Desktop on Windows Server?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • How to change the RDP listening port for Remote Desktop on Windows Server?

    Far off work area convention (RDP) is the accepted authoritative reassure access, and it might be important to make it considerably safer by changing the TCP port utilized for the system get to. It's additionally helpful when the distant PC is behind firewall which doesn't permit approaching and active associations other than standard ports or clients unfit to design the port sending for Remote Desktop in the event that they're behind firewall or switch's NAT. you can also allow remote desktop with rdp port now.

    RDP transports on TCP 3389 as a matter of course for every bolstered rendition of Windows; in the event that you need to change the port, it requires a snappy change in the Windows vault.

    Note: Editing the library is dangerous, so be certain you have a confirmed reinforcement before sparing any changes.

    Microsoft has a Knowledge Base article KB306759 that subtleties how to alter and change the Remote Desktop listening port by changing vault esteem.

    1. Start Registry Editor by tapping on Start - > Run, and type in regedit in the Run text box, and afterward press Enter or snap OK.

    2. Explore to the accompanying library branch/subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Terminal Server\WinStations\RDP-Tcp

    3. Find the library passage PortNumber in the correct sheet.

    4. Right snap on PortNumber and pick Modify (or select PortNumber, at that point click on Edit menu and select Modify).

    5. On the "Alter DWORD Value" window, click on Decimal.

    The default port task is spoken to as d3d in hexadecimal or 3389 in decimal.

    6. Type in the new port number (for example 3390) on the Value Data text box.

    7. Snap OK when done.

    It might require a reboot to make the port task produce results. When the framework is tuning in on the new port, associations need to determine the new port in the RDP customer properties, as appeared in following picture.

    The Windows Server framework will presently tune in on the new port with the Svchost.exe procedure, obvious in task chief by entering Netstat - a - n - o to see the current procedures and rundown the related executable.

  • #2
    If the idea is to connect to a computer inside a LAN from another computer that's outside that LAN (i.e. over the Internet) this is not the ideal way to do it. Ideally, there is no need to make such alterations to Windows (server or desktop).

    Getting to the LAN computer from the Internet will require going through a router at the edge of the LAN. This is where the changes should be made to allow outside access to the LAN computer. It's simply a matter of using the router's port forwarding capabilities. Pick a port # between 1025 and 65534. Using 33389 as an example, on the router create a port forward rule that re-routes port 33389 to port 3389 on the IP address of the LAN computer.

    There is no point not doing it this way. A port forwarding rule will have to be created anyway, in order to allow outside IP addresses to be routed to the local LAN computer's IP. Why not use the rule to re-route a port # as well?

    All that said, using Windows RDP (Remote Desktop Protocol) to access a LAN computer from the Internet is a bad idea. It's not secure. There are better ways to provide this capability.

    Comment

    Working...
    X