Change the Remote Desktop listening port on your computer — by Microsoft Learn

intermediatepageLink only (©)

Microsoft's steps for changing the RDP listening port from the default 3389 using PowerShell or the Registry Editor. Moving the port is a configuration tweak, not real protection, so still keep RDP off the public internet and reach it through a VPN such as WireGuard or Tailscale.

Read the full article on learn.microsoft.com

Source: Change the Remote Desktop listening port on your computer by Microsoft Learn. Licence: Link only (©).

Source reviewed: 2026-11-02
Link checked: 2026-11-02
Tested hands-on: Not by Oddbyte.Me

rdpport forwardingremote desktopsecurity

More in Remote Access (SSH, RDP, VPN)

Generating a new SSH key and adding it to the ssh-agent — by GitHub Docs

beginnerpage

Clear walkthrough for creating an Ed25519 SSH key pair, protecting it with a passphrase and loading it into ssh-agent on Linux, macOS and Windows. It is written for GitHub, but the key generation and agent steps apply to logging in to your own servers with keys instead of passwords.

Tailscale quickstart — by Tailscale

beginnerpage

Shows how to create a private tailnet by installing the Tailscale client on two devices and signing in with the same identity account, then points to follow-ups like MagicDNS, exit nodes, subnet routers and access policies. A VPN-style overlay like this is a safer way to reach home services than opening ports on your router.

Subnet routers — by Tailscale

intermediatepage

Explains how one Tailscale device can advertise a whole LAN so you can reach printers, cameras or a NAS that cannot run the client. You need IP forwarding on the router device, approval of the routes in the admin console, and access rules that permit the traffic. Approving a route does not grant access by itself.