Why some VPNs block local network access

Your VPN connects, but a printer, router page, smart TV, or shared drive on your home network stops responding. This can happen even when the internet still works. Many VPNs intentionally restrict local connections to prevent traffic from bypassing the VPN or to apply stricter security rules.

First check whether the problem is limited to your local network. The VPN Leak Test can check whether your public IP address leaks through IPv6 or WebRTC while the VPN is on. It does not test access to printers, routers, or other devices on your local network, so use it for that separate privacy check.

Check whether the VPN is blocking local access

1. Open the VPN Leak Test while connected to your VPN. It checks for public IP leaks through IPv6 or WebRTC, not whether local devices are reachable.
2. Try to open the local device in the way you normally do. For a router, you might use its local address, such as 192.168.1.1. For a printer or shared drive, use its usual app, name, or address.
3. If it fails, disconnect the VPN briefly and try the same local device again. Only do this on a network you trust, and reconnect the VPN afterward. If you must stay on the VPN, skip this comparison.
4. Try another local device, such as a second printer or a different computer's shared folder. Note whether the issue affects every local device or only one.
5. Reconnect the VPN and check its settings for an option such as Allow LAN traffic, Local network access, or Block local network. The wording and availability vary by VPN.

What the result means

Local devices work when the VPN is disconnected

The VPN or its network rules are the likely cause. Some VPNs send all traffic through the encrypted tunnel and block connections outside it, including traffic to your printer or router. Look for a local network access option in the VPN app, or ask the VPN provider whether its current mode allows LAN connections.

Local devices fail with or without the VPN

The VPN is probably not the only issue. Check that the device is powered on and connected to the same home network. A printer on a guest Wi-Fi network may be separated from your computer even though both show a Wi-Fi connection.

Only one local device fails

This points more toward that device, its address, or its own access settings than a general VPN block. Confirm that its address has not changed and that it is online. If you use a device name instead of an address, name lookup may be the part that fails.

The VPN Leak Test reports a public IP concern

That result concerns whether your public IP can be exposed through IPv6 or WebRTC while the VPN is active. It does not show that local network access is blocked, and allowing LAN access will not automatically fix a public IP leak. Review the VPN's leak protection and connection settings separately.

How to fix local access

1. Check for a local network setting in the VPN. Look for an option that allows LAN traffic or local devices. If the app offers a choice between allowing local access and blocking it, allow access only if you need those devices and trust the network. Some VPNs do not offer this option.
2. Check whether the VPN's kill switch is involved. A kill switch blocks traffic when the VPN disconnects, and some apps apply its rules broadly. Check the VPN documentation for whether local traffic can remain available while the tunnel is active. Do not turn off the kill switch on a public or untrusted network just to reach a printer.
3. Confirm that both devices are on the same network. On Windows 11, open Settings › Network & internet and check the active Wi-Fi or Ethernet connection. On macOS, open System Settings › Network. Also check that the printer or other device is not connected to a guest network that isolates devices.
4. Check the network profile and firewall rules. On Windows 11, open Settings › Network & internet › Wi-Fi or Ethernet, select the connected network, and check its network profile. On a trusted home network, a Private profile may be needed for Windows sharing and discovery. On macOS, open System Settings › Network › Firewall and review whether a firewall rule is blocking the app that needs the local device. Change firewall access only when you understand which app or service needs it.
5. Check for overlapping network addresses. A VPN network can sometimes use the same address range as your home network, for example both using addresses that start with 192.168.1. The computer may then send local-device traffic into the VPN instead. If you suspect this, contact the VPN provider or change the home router's local network range using its instructions.
6. Restart the VPN and the local device. Disconnect and reconnect the VPN, then restart the printer, router, or computer you are trying to reach. This can refresh a stale connection or address after a network change.

Why a VPN may block your home network

A VPN creates an encrypted route between your device and the VPN service. In a full-tunnel setup, internet traffic goes through that route instead of directly through your home connection. VPN software may also add firewall rules so that traffic cannot escape the tunnel if it drops. Those rules can block local traffic as well as internet traffic.

Another cause is a routing conflict. Your computer decides where to send traffic using network addresses. If the VPN and your home network use overlapping address ranges, it may not know that a printer address belongs on the home network. Local device names can also stop resolving because the VPN uses different DNS servers. DNS is the system that finds an address from a name.

Allowing local access can be a useful tradeoff at home, but it may expose devices to other people on the same Wi-Fi network. On a hotel, school, or public network, keep local access blocked unless you have a specific reason to change it.