How to Fix a VPN That Will Not Connect on Windows
Published 2026-10-16 · Marion Remote Fix
Your VPN client shows "Connecting..." and then fails, times out, or immediately disconnects after connecting. This happens with corporate VPNs (Cisco AnyConnect, GlobalProtect, Pulse Secure, Windows built-in VPN), commercial VPN services (NordVPN, ExpressVPN, Surfshark), and self-hosted VPN servers (OpenVPN, WireGuard). The fix depends on the specific error, but most VPN connection failures come from one of five causes: wrong credentials, firewall blocking, a conflicting network adapter, DNS configuration, or a protocol mismatch.
Check the basics first
- Internet connection: the VPN cannot connect if your underlying internet is down. Open a browser and load any website to confirm you have internet access without the VPN
- Credentials: re-enter your username and password. Corporate VPN credentials often expire on a schedule — check with your IT department if your password recently changed or if multi-factor authentication (MFA) is required
- VPN server: the server you are connecting to may be down or overloaded. Try a different server location if your VPN client offers multiple options. For corporate VPNs, check if there is a maintenance notification from your IT team
- Time and date: if your computer's clock is significantly wrong, SSL/TLS certificate validation will fail and the VPN handshake will be rejected. Open Settings → Time and language → Date and time → turn on Set time automatically
Restart the VPN service
VPN clients run background services that can hang or crash silently:
- Close the VPN client completely (check the system tray for the icon — right-click → Quit/Exit)
- Open Task Manager (Ctrl+Shift+Esc) and end any remaining VPN processes
- For corporate VPNs, restart the associated Windows service: press Win+R → type
services.msc→ find the VPN service (examples: "Cisco AnyConnect Socket Filter," "PanGPS," "Pulse Secure Service") → right-click → Restart - Reopen the VPN client and try connecting
Reset the network stack
Corrupted network configuration is a common cause of VPN failures, especially after Windows updates:
- Open Command Prompt as Administrator
- Run these commands in order:
ipconfig /releaseipconfig /flushdnsipconfig /renewnetsh winsock resetnetsh int ip reset
- Restart the computer and try the VPN again
Check firewall and antivirus
Firewalls can block the ports and protocols that VPN connections need:
Windows Firewall
- Open Windows Security → Firewall and network protection → Allow an app through firewall
- Find your VPN client in the list and make sure both Private and Public are checked
- If the VPN client is not listed, click "Allow another app" → Browse → navigate to the VPN executable and add it
Third-party antivirus and firewall
- Security software from Norton, Kaspersky, Bitdefender, and McAfee includes its own firewall that can block VPN traffic independently of Windows Firewall
- Temporarily disable the third-party firewall and try the VPN. If it connects, add the VPN as an exception in the security software rather than leaving the firewall disabled
Required ports
If you manage a router or corporate firewall, make sure these ports are open for outbound traffic:
- OpenVPN: UDP 1194 (default) or TCP 443
- WireGuard: UDP 51820 (default)
- IKEv2/IPSec: UDP 500 and UDP 4500
- L2TP/IPSec: UDP 1701, UDP 500, UDP 4500
- SSTP: TCP 443
- Cisco AnyConnect: TCP 443 and UDP 443 (DTLS)
Fix VPN adapter issues
VPN clients create virtual network adapters. These can conflict with each other or with physical adapters:
- Open Device Manager → expand Network adapters
- Look for VPN-related adapters (TAP-Windows Adapter, WireGuard Tunnel, WAN Miniport, Cisco VPN Adapter). If any show a yellow warning icon, right-click → Uninstall device, then reinstall the VPN client
- If you have multiple VPN clients installed, their adapters may conflict. Uninstall VPN clients you are not using
For Windows built-in VPN (Settings → Network → VPN):
- If the connection fails with error 809, 789, or 691, the WAN Miniport adapters may be corrupted. In Device Manager, uninstall all WAN Miniport entries (IKEv2, IP, IPv6, L2TP, Network Monitor, PPPOE, PPTP, SSTP), then restart. Windows recreates them on reboot
Fix specific VPN error codes
- Error 800 — VPN tunnel failed: the VPN server is unreachable. Check that the server address is correct, your internet is working, and no firewall is blocking the connection. If on a public Wi-Fi network (hotel, airport), the network may block VPN ports — try a VPN protocol that uses TCP 443 (SSTP or OpenVPN over TCP), which looks like HTTPS traffic and is rarely blocked
- Error 691 — Access denied: wrong username, password, or authentication method. Re-enter credentials. For domain networks, include the domain prefix (DOMAIN\username)
- Error 789 — L2TP/IPSec failure: the pre-shared key is wrong, or IPSec is blocked. Verify the pre-shared key matches exactly. Try switching to IKEv2 if available
- Error 720 — No PPP control protocols configured: the VPN adapter's TCP/IP configuration is broken. In Network Connections, right-click the VPN adapter → Properties → uncheck and re-check IPv4, then try again
- Error 812 — Authentication method not allowed: the VPN server requires a different authentication protocol than your client is offering. Check with your admin for the correct settings (MS-CHAPv2, EAP-TLS, etc.)
DNS problems after VPN connects
If the VPN connects but you cannot browse websites or access internal resources, DNS is likely misconfigured:
- Open Command Prompt and run
nslookup google.com. If it times out, your DNS is not working through the VPN tunnel - Try setting manual DNS: open the VPN adapter properties → IPv4 → Properties → set DNS to
8.8.8.8and8.8.4.4(Google) or1.1.1.1(Cloudflare) - For corporate VPNs, you may need to use the company's internal DNS servers (ask your IT department for the correct addresses)
- Some VPN clients have a "split tunnel" setting that determines whether all traffic goes through the VPN or just traffic for specific networks. If you can reach the internet but not internal resources (or vice versa), check the split tunnel configuration
Remote VPN troubleshooting
If your VPN connection keeps failing after trying the steps above, Marion Remote Fix can diagnose the issue remotely — checking network adapter configuration, firewall rules, DNS resolution, VPN service status, and protocol settings through a secure remote session.