VPN blocks printer access: fix this Windows 10/11 bug

You sit down to print, but Windows says “printer not reachable”

This happens every time you connect your company VPN. The printer was working fine five minutes ago. Now it's gone. You check the printer. It's on, connected to the same Wi-Fi, but your laptop just can't see it. This is a common problem with VPN clients like Cisco AnyConnect, OpenVPN, or FortiClient. The VPN takes over your network routing and blocks local devices.

Why does the VPN kill your printer?

The VPN client changes your network settings. It reroutes all traffic through the corporate tunnel. That includes traffic to devices on your home network. The printer uses a local IP address (like 192.168.1.10). But the VPN tells Windows to send all traffic through the remote gateway. So Windows can't find the printer anymore. This isn't a printer problem — it's a routing problem.

Fix: Force local traffic outside the VPN tunnel

The real fix is split tunneling. This lets local traffic bypass the VPN. Most corporate VPNs can do this, but IT often disables it for security. You have two ways to fix it. Try the first one — it's faster.

Option 1: Add a persistent route (works for most VPNs)

1. Open Command Prompt as Administrator (press Windows key, type cmd, right-click, Run as administrator).
2. Type ipconfig and press Enter. Look for your local network adapter. Find the IP address of your router (default gateway). It's usually 192.168.1.1 or 192.168.0.1.
3. Find the printer's IP address. On the printer, go to Network settings or print a configuration page. Write it down. Example: 192.168.1.20.
4. Now add a permanent route. Type:
   route -p add 192.168.1.20 mask 255.255.255.255 192.168.1.1
   Replace 192.168.1.20 with your printer's IP, and 192.168.1.1 with your router's IP.
5. Press Enter. You'll see "OK!" if it worked.
6. Reconnect the VPN and try printing again.

The -p flag makes the route permanent. It survives reboots. The mask 255.255.255.255 routes only that single IP outside the VPN. Neat, right?

Option 2: Disable automatic metric on the VPN adapter

This is a Plan B if Option 1 doesn't work. It forces Windows to prefer your local network for local addresses.

1. Open Network and Sharing Center. Type it in the Start menu.
2. Click Change adapter settings on the left.
3. Right-click your VPN adapter (usually named Ethernet 2 or TAP-Windows Adapter). Choose Properties.
4. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
5. Click Advanced. Uncheck "Automatic metric". Type 200 in the Interface metric box.
6. Click OK on all windows.
7. Do the same for your Wi-Fi adapter but give it a lower metric like 20.
8. Restart your PC and reconnect the VPN.

This tells Windows, “Hey, use the Wi-Fi for local stuff first.” It's a bit hacky but works for many people.

What if neither works?

If you still can't print, check these three things:

• Check your firewall. Windows Defender Firewall might block the printer. Go to Control Panel > Windows Defender Firewall > Allow an app through firewall. Make sure “Network Discovery” and “File and Printer Sharing” are checked for Private networks.
• Use the printer's hostname instead of IP. In Devices and Printers, right-click your printer > Printer Properties > Ports tab > Add Port > Standard TCP/IP Port. Type the printer's hostname (like HP-ENVY-4500). Sometimes hostnames route better than IPs.
• Talk to IT. I know, nobody wants to. But if your VPN forces all traffic through the tunnel, they can enable split tunneling for your home subnet (192.168.x.x). It's a 30-second change on the VPN server.

I've seen this error on Windows 10 Home, Windows 11 Pro, and even Windows 7. The fix rarely changes. Start with the persistent route. It's saved my bacon more times than I can count.