1. Check Current Routing Status#

• Execute route print to view the routing table
• Identify if the target IP is being routed to the VPN gateway
• If you see a /32 single IP pointing to the VPN, that’s usually the source of the problem

1
route print

👉 The key isn’t “if there’s a route,” but “where it leads”

2. Determine if VPN is Misrouting#

• Confirm if the target IP (e.g., 10.x.x.x) should originally go via LAN
• If the route points to the VPN gateway, it means traffic is being forcibly misrouted
• Common scenarios: misconfigured split tunnel or VPN pushing incorrect routes 👉 If DNS is normal but you can’t connect, this is usually the problem

3. Delete Incorrect Route (Quick Fix)#

• Directly delete the specified IP route
• Windows will re-select the optimal path (usually back to LAN)

1
route delete 10.1.1.10
2
route delete 10.1.1.11

👉 After deleting, re-ping / reconnect; connectivity usually restores immediately

4. (Optional) Manually Correct Route#

• If the VPN keeps overwriting, you can manually add the correct route
• Specify to go via the local gateway to prevent it from being hijacked again

1
route add 10.1.1.10 mask 255.255.255.255 192.168.1.1 metric 1

👉 Lower metric means higher priority, used to “override the VPN”