Tsallake zuwa abun ciki
Localtonet Localtonet Dashboard

Wannan shafin bai samu a cikin Hausa tukuna ba. Ana nuna shi da Turanci.

Reach Remote Desktop (RDP) through Localtonet

Taimako kan wannan shafi
A wannan shafin 8 sassa
  1. How it works
  2. Before you start
  3. Create the tunnel
  4. Open the TCP - UDP page
  5. Fill in the form
  6. Start the tunnel and copy the address
  7. Connect from outside
  8. Keep the same address
  9. Secure it
  10. Common problems
  11. Related pages

Open the desktop of a Windows PC from another network with Remote Desktop: a TCP tunnel gives port 3389 of the PC a public host name and port, with no router changes.

How it works #

The Localtonet client runs on the Windows PC you want to control, or on another device in the same network. A TCP tunnel points to the Remote Desktop port, 3389. Localtonet gives the tunnel a public address made of a host name and a port, and a Remote Desktop client that connects to that address reaches the PC. The details of TCP tunnels are on the TCP page.

Before you start #

  • A Localtonet account and the Localtonet client connected with your AuthToken on the PC. See Windows.
  • Remote Desktop turned on, on the PC you want to reach: Settings › System › Remote Desktop in Windows. Windows Home editions can't accept Remote Desktop connections.
  • A Windows account with a password on that PC. Windows refuses remote sign-ins for accounts with an empty password.
  • A Remote Desktop client on the computer you connect from: Remote Desktop Connection on Windows, or Microsoft's app for macOS, iOS and Android.

Create the tunnel #

  1. Open the TCP - UDP page #

    Open My Tunnels › TCP - UDP and expand Create TCP - UDP Tunnel.

  2. Fill in the form #

    FieldWhat to enter
    ProtocolTCP
    Device tokenThe token the Localtonet client on the PC uses.
    Server regionChoose a region close to your device for lower latency.
    Local IP address127.0.0.1 when the client runs on the PC you want to control. To reach another PC in the same network, enter its address, for example 192.168.1.20.
    Local port3389
    URL typeRandom subdomain. Custom subdomain lets you choose the name and needs Balance.

    Select Create tunnel.

  3. Start the tunnel and copy the address #

    The tunnel appears under Your tunnels. Select Start. The URL column shows the public address as host:port. Select it to copy it.

TCP or UDP - TCP? TCP is enough for Remote Desktop, and this page uses it. Remote Desktop can also use UDP on the same port as an extra transport. If you want to forward both, choose UDP - TCP in Protocol instead: that tunnel type carries TCP and UDP on one port. See UDP / TCP Mixed.

Connect from outside #

  1. On the computer you connect from, open Remote Desktop Connection (press Win + R, type mstsc, press Enter).
  2. In Computer, enter the address from the tunnel list, host and port separated by a colon: <TUNNEL_HOST>:<TUNNEL_PORT>.
  3. Select Connect and sign in with a Windows account of the remote PC.

You can also start the connection from a command line:

Command Prompt or PowerShell
mstsc /v:<TUNNEL_HOST>:<TUNNEL_PORT>

In other Remote Desktop apps, enter the same host:port value in the field for the PC name.

Keep the same address #

The host name stays with the tunnel. The port is assigned by the server when the tunnel starts. With Is Reserved? on in the tunnel's Settings, the port stays the same when the tunnel or the Localtonet client restarts, so a saved Remote Desktop connection keeps working. With it off, the port changes on a restart. Tunnels that you create while your account has Balance start with Is Reserved? on. Turning it on needs Balance and a started tunnel.

With Balance you can also choose the port under Server Port › Change, a number from 501 to 65535, as long as no other tunnel on that server uses it. See Ports.

Free plan. A TCP tunnel stops after 30 minutes on the Free plan, which ends the remote session. You can start the tunnel again, and the port can be different after each start. See Plans and Balance.

Secure it #

Do not leave Remote Desktop open to everyone. A started tunnel is reachable by anyone who has its address, and exposed RDP ports are a common target for password guessing. Restrict the tunnel before you rely on it.

  • IP Restriction. In the tunnel's Settings, select IP Restriction › Manage, choose Allow only these and add the addresses you connect from. Use my IP fills in your current address. Changes apply right away. IP Restriction needs Balance. See Access control.
  • Strong Windows passwords on every account that is allowed to sign in remotely, and Network Level Authentication left on in the Remote Desktop settings of the PC.
  • Expiration Date. For one-off support sessions, Expiration Date › Manage stops the tunnel on a date you set. See Limits and expiration.
  • Stop the tunnel when you don't need remote access.

The PC sees the Localtonet client as the source of every connection, so Windows Firewall rules that filter by remote address can't tell visitors apart. Filter by address with IP Restriction on the tunnel. Request Log › Show in the tunnel's Settings lists the connections with the visitor's IP address.

Common problems #

"Remote Desktop can't connect to the remote computer"

Check that the tunnel is started and its Connection column shows ON, that you entered the current port after the colon, and that Remote Desktop is turned on, on the PC. From the PC itself, Test-NetConnection 127.0.0.1 -Port 3389 in PowerShell shows whether the Remote Desktop port answers.

The saved connection stopped working

The port is not reserved, so it changed when the tunnel or the client restarted. Copy the new address from the tunnel list, or turn on Is Reserved?.

The session drops after half an hour

On the Free plan a TCP tunnel stops after 30 minutes. Select Start to begin another session, or add Balance to remove the session limit.

The sign-in is rejected although the password is right

The account must have a password and must be allowed to sign in through Remote Desktop: administrators are allowed by default, other accounts need to be added under Remote Desktop users in the Remote Desktop settings of the PC.

"You need to purchase balance to use this feature."

Is Reserved?, Server Port, IP Restriction and Custom subdomain need Balance. Add it under Balance.

"Port … is not available on this server."

Another tunnel on the same server uses the port you entered under Server Port. Pick a different number.

Taimako