I want to have acces to my computer remotely what is the best and most secure way to do…
- User
I want to have acces to my computer remotely what is the best and most secure way to do it ?
- Assistant
Remotely “taking over” a machine securely boils down to two pieces:
- A secure tunnel or mesh network to connect you to your LAN/host
- A hardened remote-desktop (or shell) service running on that host
Below are three widely-used patterns, from easiest to more DIY—and some hardening tips you can apply to any of them.
1. Easiest: Tailscale (WireGuard under the hood) + native RDP/SSH
Tailscale builds a zero-config WireGuard mesh between all your devices. No firewall-rewrites, no public IPs or DMZ.
• Pros:
• Peer-to-peer encrypted connections (WireGuard)
• Auto NAT traversal, no port forwarding
• Free tier for personal use (up to 20 devices)
• Works on Windows, macOS, Linux, iOS, Android• How-to at a glance:
- Sign up at https://tailscale.com
- Install the Tailscale client on both your local device and target computer
- Log in with Google/Microsoft/GitHub (you can enable SSO & 2FA)
- Your devices appear in a private network.
- On Windows hosts enable RDP (Win+R →
sysdm.cpl→ Remote → “Allow …”) - RDP/SSH to the Tailscale-assigned IP (e.g.
100.x.y.z)
2. DIY VPN + RDP or VNC
If you prefer full control, stand up your own VPN (OpenVPN or WireGuard) on your router or a small cloud VPS.
• Pros:
• You control the configuration and logs
• Can bridge into your entire LAN• Typical steps:
- Deploy WireGuard or OpenVPN on a home router/VPS
- Forward only the VPN port (e.g. UDP 51820 for WireGuard)
- Connect from your laptop → join the VPN → you’re on the LAN
- Use Windows RDP (port 3389), VNC (5900+), or SSH (22) internally
3. Cloud Jump Box + Bastion / RDP Gateway
Ideal for enterprise or multi-user setups. You expose only one hardened “bastion” in the cloud—no direct home IP.
• Pros:
• Central audit, MFA, IAM controls
• Can SSH tunnel or RDP broker through (Azure Bastion, AWS Session Manager)
Security Best Practices
Regardless of method, lock it down:
- Use key-based or token-based auth. Disable passwords where possible.
- Enforce strong 2FA/MFA on your tunnel’s management console (Tailscale, OpenVPN-AS, cloud IAM).
- Keep your OS & remote-desktop software patched.
- Change default ports; run services under non-privileged users.
- Log & monitor connections—alert on new unknown devices/IPs.
- For RDP specifically: enable Network Level Authentication (NLA).
Which to pick?
• For personal use or small office: Tailscale + native RDP/SSH
• If you want total control (and don’t mind DIY): WireGuard/OpenVPN
• In a regulated/enterprise environment: Cloud bastion/RDP gatewayLet me know your OS or any other constraints—happy to walk through step-by-step! 😊
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.