Tailscale creates a private network between devices you authorize. Install its app on the computers or phones you want to connect, sign in to the same network and test a connection. You still need the relevant file-sharing, remote-desktop or other service running on the destination.
What you need before starting
- Two supported devices with internet access.
- Permission to install the app and connect those devices.
- An account or organization that will own the private network, called a tailnet.
- A clear goal, such as reaching your home PC or a private server.
Use the current Tailscale quickstart and official downloads for each operating system. Do not paste an installation command from an old article without checking its source and supported platform.
Connect your first two devices
- Install Tailscale on the first device using the official installer or platform instructions.
- Sign in and complete the account and network setup.
- Install it on the second device and sign in to the same tailnet.
- Check that both devices appear in the device list and are online.
- Find the destination’s Tailscale address or name.
- Open the service you intend to use with that address, subject to your tailnet’s access rules.
For example, adding a PC to Tailscale does not turn on Windows Remote Desktop. The target still needs a supported Windows edition, remote access enabled and a permitted account. For attended help instead, see our Quick Assist guide.
Three features that are easy to mix up
| Feature | What it does |
|---|---|
| Device-to-device connection | Reaches an authorized device on the tailnet. |
| Subnet router | Can provide approved access to another network behind a device, when explicitly configured. |
| Exit node | Routes the selecting device’s internet traffic through the chosen exit device. |
Simply joining a tailnet does not mean all browsing now goes through your home internet connection. Tailscale’s exit-node guide explains that separate configuration. Check who owns an exit node and whether using it is appropriate before selecting one.
If the devices cannot connect
- Wrong account: confirm both devices joined the intended tailnet.
- Offline destination: wake it and check its internet connection.
- Access denied: review the tailnet policy and device approval requirements.
- Network works, app fails: check that the destination service is listening and its firewall permits the intended connection.
- Name fails: compare the device name with its assigned Tailscale address to narrow the issue.
Do not switch off every firewall to make a test pass. A private connection and permission to use a service are separate checks. Tailscale is also different from the NAT, bridged and host-only modes in a virtual machine; inspect both layers if your destination is a VM.
Review devices and plan limits
Remove access for devices you no longer own, and use access rules that match the people and services involved. Keep the app updated. Review the current plan comparison for user limits, device allowances and commercial use instead of relying on a years-old free-plan description.
Frequently asked questions
Does installing Tailscale automatically enable Remote Desktop?
No. The destination still needs the relevant remote-desktop service, supported operating system and account permissions.
Does Tailscale send all browsing through my home?
Not simply because you joined a tailnet. Routing internet traffic through another device is the separate exit-node feature.
Do I need to forward the normal Remote Desktop port on my router?
Do not add a public port forward just because you are using Tailscale. Configure the intended private route and check the destination service and policy.
Why can I see a device but not open its shared files?
The device may be online while file sharing, its firewall rule or your account permission is missing. Check the service as well as Tailscale.