How to Fix a VPN That Will Not Connect on Windows
Published 2026-10-16 · Marion Remote Fix
Your VPN will not connect — it times out trying to reach the server, connects briefly then drops, shows an authentication error, or gives a cryptic error code. VPN connection problems on Windows are caused by incorrect settings, firewall interference, outdated network drivers, DNS issues, or conflicts between VPN software and Windows networking features. This guide covers fixes for the built-in Windows VPN client, work VPNs (like Cisco AnyConnect, GlobalProtect, and Fortinet), and consumer VPN apps.
Check your internet connection first
A VPN connection requires a working internet connection underneath it. Before troubleshooting the VPN itself:
- Open a web browser and try loading a website without the VPN. If regular internet is not working, fix that first — the VPN cannot connect if there is no internet
- If you are on Wi-Fi, try switching to Ethernet or moving closer to the router. Weak Wi-Fi can cause VPN connections to fail or drop repeatedly
- If you are on a public network (hotel, coffee shop, airport), the network may be blocking VPN traffic. Some public networks block common VPN ports. Try using a different network to test
Restart the VPN and network adapter
The simplest fix that resolves many transient VPN issues:
- Disconnect from the VPN if it is stuck in a connecting state. Close the VPN application completely (check the system tray for the VPN icon and exit it)
- Disable and re-enable your network adapter: Settings → Network and internet → Advanced network settings → click your network adapter → Disable, wait 10 seconds, then Enable
- Try connecting to the VPN again. If the VPN client was stuck in a bad state, restarting the adapter clears it
- If that does not work, restart the computer. Some VPN software installs virtual network adapters that can get stuck and only reset on reboot
Fix built-in Windows VPN connection errors
If you use the VPN client built into Windows (Settings → Network and internet → VPN):
- Go to Settings → Network and internet → VPN → click your VPN connection → Advanced options. Verify that the server address, VPN type, and credentials are all correct
- Error 800 (connection failed): the VPN server is unreachable. Check the server address for typos, make sure the server is online (ask your VPN provider or IT department), and check if your firewall is blocking the connection
- Error 691 (authentication failed): wrong username or password. Re-enter your credentials. If your work password recently changed, update it in the VPN settings
- Error 809 (connection could not be established): a firewall or router is blocking the VPN ports. IKEv2 uses UDP ports 500 and 4500; L2TP uses UDP 1701, 500, and 4500; SSTP uses TCP 443. Make sure these are not blocked
- Error 720 (no PPP control protocols configured): the WAN Miniport drivers are corrupted. Open Device Manager → Network adapters → find WAN Miniport entries → uninstall each one → restart the computer. Windows reinstalls them automatically
- If the VPN type is set to Automatic, try setting it explicitly to the protocol your VPN server uses (IKEv2, SSTP, L2TP/IPsec, or PPTP). Automatic detection sometimes fails
Fix work VPN applications
Corporate VPN clients like Cisco AnyConnect, Palo Alto GlobalProtect, Fortinet FortiClient, and Pulse Secure have their own troubleshooting steps:
- Cisco AnyConnect: if you get Untrusted Server Blocked, the server certificate has changed — contact IT. If connection drops repeatedly, check if AnyConnect's VPN adapter is disabled in Device Manager → Network adapters. Also try: open AnyConnect → gear icon → Preferences → uncheck Block connections to untrusted servers (only if your IT department confirms this is safe)
- GlobalProtect: if it says the portal is unreachable, try right-clicking the GlobalProtect icon → Settings → and switching between the portal addresses if multiple are configured. A common fix is to uninstall and reinstall the GlobalProtect client
- General fix for all work VPNs: run the client as administrator (right-click → Run as administrator). Some VPN clients need elevated privileges to install their virtual network adapter or modify routing tables
- If your work VPN stopped working after a Windows Update, the update may have broken compatibility. Check with your IT department for an updated VPN client version
Check Windows firewall and antivirus
Firewalls and security software are one of the most common causes of VPN connection failures:
- Temporarily disable Windows Defender Firewall to test: Windows Security → Firewall and network protection → click your active network → toggle off Microsoft Defender Firewall. Try connecting to the VPN. If it works, the firewall is blocking the VPN
- If the firewall is the problem, add an exception rather than leaving it disabled: Windows Security → Firewall → Advanced settings → Inbound Rules → New Rule → Port → enter the VPN ports your connection uses
- Third-party antivirus (Norton, Kaspersky, Bitdefender, McAfee) often include their own firewalls that can block VPN traffic even when Windows Firewall allows it. Check your antivirus settings for a firewall or network protection section and add an exception for your VPN application
- Some antivirus programs have a dedicated VPN monitoring feature that conflicts with other VPN software. If your antivirus includes its own VPN, disable that feature when using a different VPN
Reset TCP/IP and flush DNS
Corrupted network settings can prevent VPN connections even when internet works normally:
- Open Command Prompt as administrator
- Run these commands in order:
ipconfig /flushdnsipconfig /releaseipconfig /renewnetsh winsock resetnetsh int ip reset
- Restart the computer and try connecting to the VPN again
- If the VPN connects but you cannot access anything through it (websites do not load, internal resources are unreachable), the VPN may not be setting your DNS correctly. Try manually setting DNS on the VPN adapter: Device Manager → Network adapters → find the VPN adapter → Properties → Internet Protocol Version 4 → Properties → enter your DNS server addresses
Update or reinstall network drivers
Outdated network drivers can cause VPN protocols to fail even when basic internet works:
- Open Device Manager → Network adapters
- Right-click your network adapter (Wi-Fi or Ethernet) → Update driver → Search automatically
- Also look for VPN-related adapters in the list (WAN Miniport, TAP-Windows Adapter, Cisco VPN Adapter, etc.). Update these as well
- For a clean fix: uninstall the VPN application completely, restart, update your network adapter driver from the manufacturer's website, then reinstall the VPN application fresh
Fix VPN connections that drop frequently
If the VPN connects successfully but disconnects after minutes or hours:
- Disable Wi-Fi power saving: Device Manager → Network adapters → right-click your Wi-Fi adapter → Properties → Power Management → uncheck Allow the computer to turn off this device to save power. Power saving can briefly disconnect Wi-Fi, which kills the VPN tunnel
- Keep the tunnel alive: some VPN clients have a keepalive or reconnect setting. In the Windows built-in VPN, check the connection properties → Security tab for any idle timeout settings
- Switch VPN protocols: if your VPN supports multiple protocols, try switching from UDP to TCP, or from IKEv2 to SSTP. TCP connections are more reliable on networks that interfere with UDP traffic, and SSTP uses port 443 which is rarely blocked
- Disable IPv6: some VPN connections conflict with IPv6. Open your network adapter properties → uncheck Internet Protocol Version 6 (TCP/IPv6) → OK. This forces all traffic through IPv4 which the VPN typically handles better
Fix VPN connected but no internet
If the VPN shows as connected but you cannot browse the web or reach any resources:
- Split tunneling: some VPNs route ALL your traffic through the VPN tunnel, while others only route work traffic. If your VPN uses full tunnel and the VPN server's internet is slow, everything will be slow. Check your VPN settings for a split tunneling option that lets non-work traffic use your regular internet
- DNS leak: the VPN may not be setting DNS correctly. While connected to the VPN, open Command Prompt →
nslookup google.com. If the DNS server shown is not the VPN's server, DNS is leaking to your regular connection. Set DNS manually on the VPN adapter - MTU mismatch: VPN tunneling adds overhead to each packet. If packets are too large, they get dropped silently. Open Command Prompt →
netsh interface ipv4 set subinterface "Your VPN Adapter Name" mtu=1400 store=persistent. Try values between 1300 and 1400
Remote VPN troubleshooting
If your VPN still will not connect after trying these fixes, Marion Remote Fix can diagnose the problem remotely — checking network configuration, firewall rules, adapter drivers, and VPN client settings through a secure remote session.