How to Fix a VPN Connection That Keeps Failing on Windows
Published 2026-10-16 · Marion Remote Fix
Your VPN will not connect. You click connect and it times out, gives an error code, or connects briefly then drops. This happens with the Windows built-in VPN client, corporate VPN solutions like Cisco AnyConnect or GlobalProtect, and commercial VPN apps like NordVPN, ExpressVPN, and Surfshark. The cause is usually a network setting, a conflicting adapter, a firewall rule, or a protocol mismatch. Here is how to diagnose and fix VPN connection failures on Windows.
Check your internet connection first
A VPN needs a working internet connection before it can establish its encrypted tunnel:
- Disconnect from the VPN and open a web browser. Can you load any website? If not, fix your internet first — the VPN is not the problem
- Try a different website. If only specific sites are unreachable, your ISP may be having routing issues
- If you are on Wi-Fi, try an Ethernet cable. Unstable Wi-Fi connections cause VPN timeouts because the VPN handshake requires sustained packet exchange
- Restart your router if your connection is slow or dropping. Power off for 30 seconds, then power back on and wait for it to fully reconnect
Restart the VPN service
The VPN client service may be stuck or not running:
Windows built-in VPN
- Press Win+R → type
services.msc→ Enter - Find these services and make sure each is running (right-click → Start if stopped):
- IKE and AuthIP IPsec Keying Modules (for IKEv2 VPN)
- IPsec Policy Agent
- Remote Access Connection Manager
- Routing and Remote Access (set to Manual, start only if needed)
Third-party VPN apps
- Close the VPN app completely (check the system tray — right-click the icon → Quit/Exit)
- Open Task Manager (Ctrl+Shift+Esc) → look for any remaining VPN processes → End task
- Reopen the VPN app and try connecting
Try a different VPN server or protocol
The specific server you are connecting to may be down, overloaded, or blocked:
- In your VPN app, switch to a different server location. If you were connecting to a specific city, try another server in the same country
- Change the VPN protocol. Most VPN apps offer multiple protocols:
- WireGuard: fastest, most reliable on modern networks. Try this first if available
- OpenVPN (UDP): reliable and widely supported. UDP is faster but can be blocked
- OpenVPN (TCP): slower but works through more firewalls since it uses the same port as HTTPS (443)
- IKEv2: good for mobile and switching between Wi-Fi and cellular. Built into Windows
- L2TP/IPsec: older, may be blocked by NAT firewalls. Try only if others fail
- SSTP: Microsoft protocol that tunnels through HTTPS (port 443). Works through almost any firewall
- If UDP protocols time out, your network may be blocking UDP traffic. Switch to a TCP-based protocol (OpenVPN TCP or SSTP)
Fix Windows built-in VPN error codes
The Windows VPN client gives specific error codes that point to the cause:
| Error Code | Meaning | Fix |
|---|---|---|
| 691 | Wrong username or password | Re-enter credentials. Check for caps lock. Verify account is active with your VPN provider |
| 800 | Cannot reach the VPN server | Check internet, verify server address, check firewall is not blocking VPN ports |
| 809 | Network connection between your computer and the VPN server could not be established | Enable IPsec passthrough on your router. Open UDP ports 500 and 4500 in your firewall |
| 812 | Server policy prevents connection | Contact VPN administrator — authentication method or encryption mismatch |
| 720 | Cannot negotiate a compatible set of network protocols | Reinstall WAN Miniport adapters (see below) |
| 789 | L2TP connection attempt failed because the security layer could not authenticate | Set pre-shared key correctly. Check IKE service is running. Enable IPsec on router |
| 628/651 | Connection was closed by the remote computer | Server rejected the connection — check credentials, try different server, contact admin |
Disable conflicting network adapters
Other VPN clients, virtual network adapters, and certain software create network adapters that can conflict with your VPN connection:
- Open Device Manager → expand Network adapters
- Look for old or unused VPN adapters: TAP-Windows adapters from old OpenVPN installs, Cisco adapters from uninstalled AnyConnect, Hyper-V virtual switches, or VMware/VirtualBox adapters
- Right-click unused adapters → Disable device (not Uninstall, in case you need them later)
- Try connecting to your VPN again
If you recently uninstalled a VPN app, it may have left behind ghost adapters. Uninstalling these in Device Manager can resolve conflicts.
Reset WAN Miniport adapters
The Windows built-in VPN uses WAN Miniport virtual adapters for each protocol. If these are corrupted, VPN connections fail:
- Open Device Manager → expand Network adapters
- You should see WAN Miniport (IKEv2), WAN Miniport (IP), WAN Miniport (L2TP), WAN Miniport (PPTP), WAN Miniport (SSTP), and others
- Right-click each WAN Miniport adapter → Uninstall device
- Restart the computer. Windows automatically recreates the WAN Miniport adapters on boot
- Try the VPN connection again
Configure firewall and antivirus
Firewalls and security software can block VPN traffic:
- Temporarily disable your third-party firewall or antivirus (Norton, Kaspersky, Bitdefender, McAfee) and test the VPN. If it connects, add the VPN app as an exception in your security software
- Windows Firewall: make sure these ports are not blocked:
- IKEv2: UDP 500 and UDP 4500
- L2TP/IPsec: UDP 500, UDP 4500, and UDP 1701
- OpenVPN: UDP 1194 (default) or TCP 443
- SSTP: TCP 443
- PPTP: TCP 1723 and GRE protocol 47
- WireGuard: UDP 51820 (default)
- On corporate networks, the network firewall (not your PC) may block VPN traffic. Ask your network admin, or try connecting from a different network (mobile hotspot) to test
Flush DNS and reset network stack
Stale DNS cache or corrupted network configuration can prevent VPN connections:
- Open Command Prompt as Administrator
- Run these commands in order:
ipconfig /flushdnsipconfig /registerdnsnetsh winsock resetnetsh int ip reset
- Restart the computer after running these commands
- Try the VPN connection again
Fix DNS leaks and split tunneling
If the VPN connects but websites do not load, DNS may not be routing through the VPN tunnel:
- Check your VPN app settings for a DNS leak protection or DNS settings option — enable it
- If using the Windows built-in VPN, manually set DNS on the VPN adapter: Network Connections → right-click VPN connection → Properties → IPv4 → Properties → use your VPN provider's DNS servers
- Split tunneling (where some traffic goes through VPN and some through your regular connection) can cause routing conflicts. Try disabling split tunneling temporarily to test — force all traffic through the VPN
Check router NAT and passthrough settings
Some routers block VPN protocols by default:
- Log into your router admin page (usually 192.168.1.1 or 192.168.0.1)
- Look for VPN Passthrough settings (often under Security or Advanced):
- Enable IPsec Passthrough (for IKEv2 and L2TP)
- Enable PPTP Passthrough (for PPTP)
- Enable L2TP Passthrough (for L2TP)
- If your router has a Strict NAT type, VPN connections may fail. Try enabling UPnP or setting your computer as a DMZ host temporarily to test
- Some ISP-provided routers have limited VPN support. If your ISP router blocks VPN traffic and you cannot change the settings, connect your own router behind the ISP router
Reinstall the VPN client
If nothing else works, a clean reinstall of the VPN app can fix persistent connection issues:
- Uninstall the VPN app from Settings → Apps → Installed apps
- Restart the computer
- Open Device Manager → Network adapters → remove any leftover TAP or TUN adapters from the old installation
- Download the latest version of the VPN app from the provider's website
- Install and configure from scratch. Do not import old configuration files — they may contain settings that caused the failure
Remote VPN troubleshooting
If your VPN keeps failing and the fixes above have not resolved it, Marion Remote Fix can diagnose the issue remotely — checking adapter configuration, resolving protocol and firewall conflicts, resetting the network stack, and testing connectivity through a secure remote session.