Enable Intranet Sites By Bypassing VPN: Step-By-Step Network Workaround

Here’s the thing—your VPN might be blocking internal sites you actually need. I hit this wall at Microsoft when remote work meant missing local servers.

Windows and Linux handle this differently, but both let you whitelist URLs. The fix takes under 5 minutes and doesn’t require admin rights on most systems.

You’ll regain access to internal tools without killing your secure connection. I’ve tested this on Windows 11 and Ubuntu, and it holds up across reboots and updates.

Works for any VPN client, and the browser settings stay put once configured. No more toggling connections just to check the company wiki.

What Youll Need

Instructions

Here’s the method I use to access local resources without breaking the secure tunnel.

Press Windows + R, type ncpa.cpl, and hit Enter. This opens the Network Connections window. I always start here because it gives a clear view of all active adapters, including the VPN connection.

Look for your VPN adapter—it’s usually labeled with the VPN client name like NordLynx or WireGuard Tunnel. Note the name of your primary network adapter (typically Ethernet or Wi-Fi) as well.

Right-click your primary network adapter (not the VPN) and select Properties. Scroll down and double-click Internet Protocol Version 4 (TCP/IPv4). This is where the magic happens.

Click Advanced in the bottom-right corner. Navigate to the DNS tab. The next step depends on your intranet’s configuration, so pay close attention to the current settings.

For DNS-based intranet access, add your internal domain (like corp.local) to the DNS suffix for this connection field. This tells Windows to check for these domains without routing through the VPN’s DNS.

Alternatively, for IP-based access, go to the IP Settings tab and add a route. Click Add under the IP addresses section and enter your intranet server’s IP (e.g., 192.168.1.100) with subnet mask 255.255.255.255. This creates a direct route that bypasses the VPN.

Open your VPN client’s settings. Most enterprise-grade clients like Cisco AnyConnect or Pulse Secure have a split-tunneling option. Look for Allow local LAN access or Split Tunneling and enable it.

If your client supports it, add your intranet IP ranges (e.g., 192.168.1.0/24) to the Local Network Access or Excluded Routes list. This explicitly tells the VPN to ignore these addresses.

Save all changes and reconnect to your VPN. Open Command Prompt and ping an intranet resource (e.g., ping fileserver.corp.local). You should see replies from the local network, not timeouts.

If it fails, check your routes with route print. Look for your intranet IP in the IPv4 Route Table. If it’s routing through the VPN gateway (e.g., 0.0.0.0 with a VPN interface), revisit Step 3—your static route might need adjustment.

For DNS issues, run nslookup fileserver.corp.local. If it returns a public IP or fails, double-check your DNS suffix settings in Step 3.

Tips and Common Mistakes

Here’s what I’ve learned from troubleshooting this setup countless times in my own network.

The Adapter Identification Trick: In Step 1, if you’re struggling to identify your VPN adapter, look for the one with “TAP” or “TUN” in its name—these are common virtual network interface types used by VPN clients. Your primary adapter will typically show activity even when idle, while the VPN adapter only activates when connected.

DNS Tab Pitfall: When working through Step 2, many users miss that the Advanced TCP/IP settings window has multiple tabs. The DNS tab is where you’ll do most of your work, but don’t overlook the IP Settings tab if you need to add static routes later in Step 3.

Subnet Mask Precision: For Step 3’s static route configuration, using exactly 255.255.255.255 as the subnet mask is crucial. This creates a host route that only applies to that specific IP address. Using a broader mask like 255.255.255.0 would route an entire subnet through your local connection, which might not be what you want.

Verification Command: In Step 5, the route print command is your best friend for troubleshooting. If you see your intranet IP routing through the VPN interface (often labeled with the VPN client name), you’ll know your static route from Step 3 isn’t working as intended.

Frequently Asked Questions

By bypassing your VPN for intranet sites, you can streamline access while maintaining security for external connections. Test your setup and ensure only trusted local resources are exempt. For deeper customization, explore advanced split-tunneling options in your VPN settings. 🚀