VPN Connects but No Internet in Windows? Fix It with Split Tunneling

Your VPN shows Connected in Windows, but websites won’t load and apps can’t reach the internet.

Why: By default a Windows VPN profile sends all your traffic through the tunnel (force tunneling). If the VPN server only routes its own private network — not the public internet — everything else dies the moment you connect. The fix is split tunneling: only traffic for the remote intranet goes through the VPN, and normal internet traffic uses your regular connection. (Only do this if your security policy allows it — some workplaces require full tunneling on purpose.)

Fix 1: Enable split tunneling (PowerShell)

Split tunneling is set per-profile via PowerShell. Open PowerShell as administrator:

Get-VpnConnection                                  # find your profile's exact Name
Set-VpnConnection -Name "Work VPN" -SplitTunneling $True -PassThru

When split tunneling is enabled, traffic to destinations outside the intranet no longer flows through the VPN tunnel — so your internet keeps working while connected. The -PassThru output should show SplitTunneling : True. Disconnect and reconnect the VPN for it to take effect.

To go back to routing everything through the VPN, set it to $False:

Set-VpnConnection -Name "Work VPN" -SplitTunneling $False -PassThru

Fix 2: Verify the “default gateway on remote network” setting

The classic UI equivalent of split tunneling lives in the legacy adapter properties:

1. Press Windows key + R, type ncpa.cpl, press Enter.
2. Right-click your VPN adapter > Properties > Networking tab.
3. Select Internet Protocol Version 4 (TCP/IPv4) > Properties > Advanced.
4. On the IP Settings tab, the Use default gateway on remote network checkbox controls this. Cleared = split tunneling (your local gateway handles internet); ticked = all traffic via VPN.

This mirrors Fix 1 — use whichever you prefer. After changing it, reconnect the VPN.

Fix 3: Flush DNS and retry

Even with routing fixed, stale DNS can leave pages unreachable. In Command Prompt as administrator:

ipconfig /flushdns

Then disconnect and reconnect the VPN. If names still don’t resolve only while on the VPN, the issue is the DNS server the VPN pushes — confirm with your admin that it’s reachable, or set a DNS suffix on the profile so internal names resolve correctly.

FAQ

Is split tunneling safe? It’s a trade-off. It keeps your internet fast and working, but traffic outside the intranet isn’t protected by the VPN. Many workplaces deliberately force-tunnel everything for security — check your policy before changing it.

It still has no internet after enabling split tunneling. Reconnect the VPN (the change only applies to new sessions), then flush DNS (Fix 3). If it persists, the VPN server itself may not be advertising routes correctly — that’s a server-side configuration for your admin.

Where’s the split-tunneling toggle in Settings? There isn’t a simple on/off switch in the modern Settings app — Windows exposes it through PowerShell (Set-VpnConnection -SplitTunneling) and the legacy ncpa.cpl adapter properties shown above.

Sources: Microsoft Learn — Set-VpnConnection (VpnClient)