For most people, the safest way to reach IoT devices from a Windows 11 PC when you’re not on the same network is to put your PC and the devices on a private mesh VPN (such as Tailscale or ZeroTier) or your own WireGuard VPN, then connect with Windows 11’s built-in SSH client (for Linux-based devices) or Remote Desktop/VNC (for devices with a desktop). Avoid opening ports on your router directly to the internet. The same setup works for smart home hubs, cameras and a Raspberry Pi.

Step 1: Choose How to Reach the Device
- Mesh VPN (easiest): install a service like Tailscale or ZeroTier on your Windows PC and on the device. Each gets a private address that works from anywhere, without router changes. Many have free personal plans.
- Your own VPN: run WireGuard or OpenVPN on your router or a home server, then connect your PC to it when you’re away.
- Vendor cloud app or dashboard: many consumer devices (cameras, thermostats, hubs) are designed to be managed through the maker’s app or website. This is usually the simplest option for those devices.
- IoT platforms: for fleets of devices, services such as Azure IoT Hub, AWS IoT or similar platforms provide device management and secure remote access.
- Port forwarding (not recommended): exposing SSH, RDP or a device’s web page directly to the internet invites constant attacks. If you must, use strong keys, a non-default port, and restrict access by IP.
Is remote access to IoT devices free?
Built-in tools and many VPN options are free for personal use. Cloud IoT platforms charge based on usage.
Can I access devices without a static IP?
Yes. Mesh VPNs work without a static IP. For your own VPN, use dynamic DNS to track your home address.
Step 2: Connect With SSH (Linux-Based Devices)
- Make sure SSH is enabled on the device (for example, Raspberry Pi OS lets you enable it in its configuration settings).
- On Windows 11, open Terminal (right-click Start > Terminal).
- Connect with
ssh -l username device-address, for examplessh -l admin 100.84.12.7using the device’s VPN address. - Type yes the first time to trust the device’s key, then enter the password or key passphrase.
For better security, create an SSH key with ssh-keygen -t ed25519, copy the public key to the device’s ~/.ssh/authorized_keys file, and turn off password logins on the device. See how to use SSH to reach IoT devices from anywhere for more detail.
Step 3: Remote Desktop or VNC (Devices With a Screen)
- Windows IoT devices: enable Remote Desktop on the device, then use the Remote Desktop Connection app (mstsc) on Windows 11 with the device’s VPN address.
- Linux devices with a desktop: enable a VNC server (or an RDP server such as xrdp) and connect with a VNC viewer or Remote Desktop from Windows.
Step 4: Web Dashboards
Many devices, like routers, home automation hubs and printers, have a web page for settings. Over your VPN, type the device’s private address into your browser (for example, http://100.84.12.7:8123 for a home automation hub). Don’t expose these dashboards directly to the internet.
Security Checklist
- Change default usernames and passwords on every device.
- Keep device firmware and your Windows PC up to date.
- Use SSH keys or multi-factor authentication where possible.
- Put IoT devices on a separate guest or IoT network if your router supports it.
- Turn off remote-access features you don’t use.
If the Connection Fails
- “Connection timed out”: check that both devices are online in the VPN app, and that the device’s SSH or RDP service is running.
- “Permission denied”: check the username, password or key, and that the key’s permissions are correct on the device.
- ssh isn’t recognized: install OpenSSH Client in Settings > System > Optional features.

Kermit Matthews runs Live2Tech from just outside Philadelphia. He is an IT specialist with over 20 years of experience, from a university help desk to small-business IT, IT management and his own consulting practice, and has written tech guides full time since 2020. Steps are checked against the current software on a real device or the maker’s official documentation. More about Kermit.