You set up Tailscale to Remote Desktop into your home PC from outside, but when you actually need it, it won’t connect.
Short answer: first run tailscale ping on the PC you’re connecting from. No reply means a Tailscale-side problem (disconnected after a restart, an expired key, sleep, etc.); a reply but still no connection means a Windows-side problem (Remote Desktop settings, firewall, credentials). The most common case is the home PC restarting, dropping Tailscale; turning on Run unattended prevents it. Setup steps are in Remote Desktop to your home PC with Tailscale, no port forwarding (in Japanese).
First, narrow it down: Tailscale or Windows?
Open PowerShell on the PC you’re connecting from, such as your laptop. Run the three commands below in order, replacing desktop-pc with the target PC’s machine name, as shown under Machines in the Tailscale admin console.
tailscale status tailscale ping desktop-pc Test-NetConnection desktop-pc -Port 3389
If the tailscale command isn’t found, run it by full path, e.g. & "C:\Program Files\Tailscale\tailscale.exe" status.
tailscale status: lists the devices in your tailnet. If the target PC’s row saysoffline, Tailscale isn’t running there. If it isn’t listed at all, access controls may be hiding ittailscale ping: checks whether the target is reachable using only the Tailscale route. Apongmeans the route works. It also shows whether it’s direct or via a relay server (DERP)Test-NetConnection: checks whether port 3389, used by Remote Desktop, is reachable.TcpTestSucceeded=Truemeans the target’s Remote Desktop accepts connections
How to read Test-NetConnection is covered in detail in how to check whether a port is reachable (in Japanese).
Reading the results:
tailscale pinggets no reply: a Tailscale-side problem. Go to “Things to check on the Tailscale side”tailscale pingreplies, butTcpTestSucceededisFalse: the route works, but the target PC isn’t accepting port 3389. See causes 6, 7 under “Things to check on the Windows side”- Both pass, yet Remote Desktop won’t let you in: almost always credentials (user name, password). See cause 8
Things to check on the Tailscale side
Cause 1: the target PC restarted or signed out, dropping Tailscale
This is the easiest one to fall into. By default, Tailscale on Windows stays connected only while a user is signed in. If Windows Update restarts it overnight, or you close Remote Desktop by “signing out”, it stays disconnected until someone signs in again.
The fix is to enable Tailscale’s Run unattended, which keeps it connected even with nobody signed in. On the home PC, do one of these:
- Right-click the Tailscale icon in the system tray → “Preferences” → “Run unattended”, then press “Yes” when asked. A check mark means it’s on
- Run this command in PowerShell or Command Prompt
tailscale set --unattended=true
The Windows account that enables it becomes the owner of the Tailscale settings; other users can no longer change them. Once enabled, sign out once to confirm tailscale ping still replies.
Cause 2: the Tailscale key expired
Tailscale device keys expire after 180 days by default. Once expired, the device drops off the tailnet until you log in again, so one day it just stops connecting.
Open Machines in the Tailscale admin console to see each device’s key expiry. If it expired, log in to Tailscale again on that device.
For a PC that stays at home, “…” → “Disable key expiry” under Machines keeps it from stopping. Not a good setting for a laptop you carry around.
Cause 3: the target PC is asleep or hibernating
If the target PC is asleep or hibernating, you can’t connect from outside, nor can Tailscale wake it.
On Windows 11, under Settings → System → Power (laptops: “Power & battery”), set the time before sleep when plugged in to “Never”. The screen-off time can stay short.
Cause 4: a new device is waiting for Device Approval
If Device Approval is enabled in the admin console, newly added devices can’t talk to tailnet devices until an admin approves them. If it stopped connecting right after you replaced your laptop or reinstalled Tailscale, check under Machines whether that device is awaiting approval, then approve it.
If you’ve edited your tailnet’s access controls (the Access controls policy) yourself, check that they aren’t blocking the traffic. With the defaults, devices in the same tailnet can talk to each other.
Cause 5: the MagicDNS name doesn’t resolve
If tailscale ping fails with a machine name, name resolution may be the problem. Try tailscale ping again with the 100.x.x.x Tailscale IP shown under Machines. If the IP works, suspect your MagicDNS settings, or a mistyped machine name (e.g. the PC was renamed).
You can also find the target PC’s Tailscale IP by running this on it:
tailscale ip -4
You can enter this IP instead of the MagicDNS name as the computer name in Remote Desktop Connection, too.
Things to check on the Windows side
If tailscale ping replies, the route works, so check the target PC’s Windows settings (once you’re home, or over SSH).
Cause 6: Remote Desktop is off, or it’s Home edition
Check that Settings → System → Remote Desktop is on. Only Pro or higher can accept connections; Home doesn’t have this setting (connecting from Home is fine).
Cause 7: the firewall blocks port 3389
If tailscale ping replies but TcpTestSucceeded is False, suspect the target PC’s firewall. Enabling Remote Desktop also enables Windows Defender Firewall’s “Remote Desktop” rules, but depending on which network type (profile) those rules apply to, traffic over Tailscale can be blocked.
On the target PC, check these two in an administrator PowerShell. The first shows which profile (NetworkCategory) the Tailscale network has; the second shows which profiles the Remote Desktop rules are enabled for.
Get-NetConnectionProfile | Select-Object InterfaceAlias, NetworkCategory Get-NetFirewallRule -Group "@FirewallAPI.dll,-28752" | Select-Object DisplayName, Enabled, Profile
Tailscale normally sets its network to “Private”. If the row with InterfaceAlias Tailscale says Public, with the Remote Desktop rules not enabled for Public, change the Tailscale network to Private:
Set-NetConnectionProfile -InterfaceAlias Tailscale -NetworkCategory Private
If you use a third-party security suite’s firewall, check that it isn’t blocking inbound port 3389 too.
Cause 8: user name, password (credentials) rejected
If you get as far as the connection screen but see “Your credentials did not work” or a logon failure, it’s an authentication problem, not Tailscale.
If you sign in with a Microsoft account, enter its email address as the user name, with the Microsoft account password. The PIN or face recognition (Windows Hello) you use to unlock the screen can’t sign you in to Remote Desktop.
Also, if Settings → Accounts → Sign-in options has “For improved security, only allow Windows Hello sign-in for Microsoft accounts on this device” turned on, even the password may be rejected. In that case, try this on the target PC:
- Turn off that “only allow Windows Hello sign-in” option
- Lock (or sign out) once, choose the password in sign-in options, then sign in with the password
- Connect over Remote Desktop again
All of these are done at the target PC, so it’s safest to test a connection from inside your home once before you go out.
With SSH, you can check the cause from outside
With OpenSSH Server installed on the home PC, if tailscale ping replies you can SSH in to check causes 6, 7 on the spot. Run these after logging in to see the Remote Desktop service, plus whether port 3389 is listening:
Get-Service TermService Get-NetTCPConnection -LocalPort 3389 -State Listen
If Tailscale itself is down (causes 1-3), SSH won’t get in either, so set up Run unattended plus the sleep settings beforehand.
Summary
- Start with
tailscale ping. No reply: check restart/sign-out (Run unattended prevents it), key expiry, sleep, pending approval - Reply, yet port 3389 fails: Remote Desktop settings, the firewall
- Rejected at the connection screen: the Microsoft account password, the “Windows Hello sign-in only” setting


コメント