VPN Won't Connect From Home? Fix in 5 Minutes

Quick Answer for Advanced Users

Change your VPN protocol to SSTP (port 443) or enable split tunneling. Check router VPN passthrough settings for L2TP/IPsec. If you're on a double NAT (ISP router + your router), bridge one of them.

Why This Happens

Your company VPN drops at home because home routers and ISPs love to mess with VPN traffic. The culprit here is almost always one of three things: your router blocks VPN ports (especially PPTP on 1723 or L2TP on 500/4500), your ISP throttles or blocks VPN protocols, or you're behind double NAT (two routers in a row). I've seen this exact issue with Windows 11 clients connecting to a Cisco AnyConnect or OpenVPN server. The user can browse the web fine, but VPN times out. Don't bother with reinstalling the VPN client – it rarely helps. The problem is between your PC and the internet.

Step-by-Step Fix

Check which VPN protocol you're using. Open your VPN client settings. If it's PPTP (old and insecure), switch to L2TP/IPsec or SSTP. PPTP is blocked by many home routers by default. If your company forces PPTP, you'll need to open port 1723 in your router.
Enable VPN passthrough on your router. Log into your router admin panel (usually 192.168.1.1 or 192.168.0.1). Look for "VPN Passthrough" or "IPsec Passthrough" under Advanced > Security or Advanced > VPN. Enable it. This is a common setting on TP-Link, Netgear, and ASUS routers. Save and reboot both router and PC.
Change VPN port to 443 (SSTP). If your VPN client supports SSTP (most do, including Windows built-in), switch to it. Port 443 is used by HTTPS – your ISP won't block it. On Windows: Settings > Network & Internet > VPN > Change adapter options > right-click your VPN > Properties > Security > Type of VPN: SSTP. This fix works 80% of the time.
Enable split tunneling. This forces only work traffic through VPN, not your whole internet. It reduces packet loss and stops your ISP from seeing a constant VPN stream. In your VPN client, look for "Split Tunneling" or "Route only specific IPs through VPN". If your company allows it, enable it. If not, skip this one.
Flush DNS and reset network stack. Open Command Prompt as admin (Win+X, then A). Run these commands:
```
ipconfig /flushdns
netsh winsock reset
netsh int ip reset
ipconfig /renew
```
Then restart your PC. This clears wonky DNS entries that sometimes cause VPN timeouts.
Try a different UDP port. For L2TP/IPsec, change the server port from 500 to 4500 (if your VPN admin allows it). Many ISPs block port 500. Check with your IT team first.

Alternative Fixes If Main Steps Don't Work

Double NAT issue: If your home has a modem from your ISP (like a combo modem/router) connected to your own router, you have two routers. This confuses VPN. Fix: put your router into Access Point mode, or put the ISP modem into bridge mode. Call your ISP for bridge mode instructions – it's usually a setting in the admin panel.

ISP blocking: Some ISPs (like some in the UK or Australia) block VPN traffic outright. Test by connecting your PC directly to the ISP modem (remove your router). If VPN works, your router is the problem. If it still fails, call your ISP and ask "Do you block VPN protocols?". They might have a "VPN friendly" setting.

Use a different VPN client: If your company uses OpenVPN, try the OpenVPN Connect app instead of the Windows built-in client. Third-party clients often handle NAT better. Also, try a mobile hotspot (cellular) to bypass your home network entirely – if VPN works there, it's definitely your router or ISP.

TCP port 443 with OpenVPN: If your VPN admin can change the server config to use TCP 443 instead of UDP 1194, do it. TCP is more reliable through NAT and firewalls. UDP is faster but gets blocked more often at home.

Prevention Tip

Once you get it working, set a static IP for your PC in your router's DHCP reservation. This stops IP changes from breaking the VPN later. Also, keep your router firmware updated – VPN passthrough bugs are common in older firmware versions. If you're the admin, enable SSO (Single Sign-On) with certificate-based authentication – it bypasses many home network issues because it uses HTTPS tunnels.

One last thing: test your VPN connection every few months from a coffee shop or friend's house. If it works there but not at home, it's your home network. You already know what to do now.