VPN breaks local network access

Problem summary

A VPN can intentionally block local network access or route traffic away from home devices.

When to worry

• Local printers or shares work until the VPN connects.
• The router admin page is unreachable only while VPN is active.
• A work VPN is involved and the device is managed.

Fast checks

• Confirm the local device works with VPN disconnected.
• Check whether the VPN has a local network access or split tunneling setting.
• Try the device by stable local IP instead of discovery name.
• Capture the exact VPN name and policy message if shown.

Likely causes

• The VPN blocks LAN access by policy.
• Local discovery traffic does not pass through the VPN state.
• The local subnet overlaps with the remote network subnet.
• Work management prevents changing the setting.

Step-by-step fix

1. 1Test local access before and after connecting VPN.
2. 2Use the device's reserved IP address for a direct test.
3. 3Enable local network access only if the VPN owner allows it.
4. 4If subnet overlap is suspected, record the home router LAN range before changing anything.
5. 5For work VPNs, ask support whether local LAN access is allowed.

What not to do

• Do not bypass a work VPN policy.
• Do not expose local printers, NAS, or cameras to the internet.
• Do not change router subnet while backups or work devices are active unless you understand the impact.

When to stop/get help

• Stop if the VPN is required by work or school.
• Stop before changing security, firewall, or routing settings you cannot reverse.
• Get help if business VPN and home subnet overlap are both involved.

Related tool/checklist

Use the linked tool when you need a guided plan from your exact symptoms instead of a static checklist.

Related problems

Last reviewed

2026-05-06

Sources/assumptions

• Assumes a trusted home LAN and a consumer or work VPN client.
• VPN owner policy is the final source for managed devices.