How to Fix VPN Connection Issues on Windows
Published 2026-10-16 · Marion Remote Fix
Your VPN will not connect — it times out, shows an authentication error, connects but you cannot reach anything, or it drops repeatedly after a few minutes. VPN connection failures on Windows have specific causes depending on whether you use a built-in Windows VPN, a third-party client like NordVPN or ExpressVPN, or a corporate VPN. Here is how to diagnose and fix it.
Check your internet connection first
A VPN cannot connect if your underlying internet is down or unstable:
- Disconnect the VPN completely and try loading a website in your browser. If regular internet does not work, fix that first — the VPN is not the problem
- Try a different website. Some sites may be down independently
- If you are on Wi-Fi, try moving closer to the router or switching to a wired Ethernet connection. Unstable Wi-Fi causes VPN timeouts because VPN protocols are sensitive to packet loss
- Restart your router by unplugging it for 30 seconds and plugging it back in. Wait two minutes for it to fully boot before testing
Verify your VPN credentials
Incorrect credentials are the most common cause of VPN authentication failures:
- Re-enter your username and password manually instead of relying on saved credentials. Copy-paste can introduce invisible characters
- Check if your VPN subscription has expired or if your account has been locked due to too many failed login attempts
- For corporate VPNs, confirm with your IT department that your account is active and that your credentials have not been reset
- If your VPN uses certificate-based authentication, check that the certificate has not expired. Open
certmgr.mscand look under Personal → Certificates for your VPN certificate's expiration date
Restart the VPN client
VPN applications can get into a stuck state where they cannot establish new connections:
- Close the VPN application completely — check the system tray near the clock and right-click the VPN icon to exit or quit
- Open Task Manager (Ctrl+Shift+Esc) and end any remaining VPN processes (look for the VPN name or openvpn.exe, wireguard.exe, etc.)
- Reopen the VPN application and try connecting again
- If the client crashes repeatedly, uninstall and reinstall it from the VPN provider's official website
Check Windows built-in VPN settings
If you use the Windows built-in VPN client (Settings → Network and Internet → VPN):
- Verify the server address is correct — a single wrong character prevents connection
- Check the VPN type matches what your VPN server expects: IKEv2, L2TP/IPsec, SSTP, or PPTP. Using the wrong protocol always fails
- For L2TP/IPsec, enter the pre-shared key under Advanced options. A missing or wrong key causes immediate authentication failure
- Try setting the VPN type to Automatic if you are unsure which protocol the server uses
Fix firewall and antivirus blocking VPN
Firewalls and antivirus software frequently block VPN connections because VPN traffic looks unusual:
- Temporarily disable your firewall and antivirus, then try connecting. If the VPN works with them off, you need to add an exception
- Add your VPN application to the firewall's allowed apps list (Settings → Privacy and Security → Windows Security → Firewall and network protection → Allow an app through firewall)
- Some antivirus suites have their own firewall that overrides Windows Firewall. Check your antivirus settings for network protection or firewall sections
- If you are on a corporate or school network, the network administrator may be blocking VPN protocols at the router level. Try a different network to confirm
Change the VPN protocol
Different VPN protocols use different ports and encryption methods. If one protocol is blocked, another may work:
- OpenVPN TCP port 443: this uses the same port as HTTPS web traffic, making it very difficult for networks to block without also blocking all websites. Most VPN clients let you switch to TCP 443 in settings
- WireGuard: lightweight and fast, but uses UDP which some networks block. If WireGuard fails, switch to OpenVPN
- IKEv2: good for mobile and Wi-Fi switching but uses UDP ports 500 and 4500 which are sometimes blocked
- L2TP/IPsec: older protocol, uses UDP port 1701. Commonly blocked on public networks. Avoid if other options are available
- Check your VPN client's settings or preferences for a protocol selection option. Try each protocol if the default fails
Flush DNS and fix DNS leaks
DNS issues can cause a VPN to connect but leave you unable to reach websites:
- Open Command Prompt as administrator
- Run
ipconfig /flushdnsto clear the DNS cache - Run
ipconfig /releasethenipconfig /renewto refresh your network configuration - Run
netsh winsock resetand restart your computer. This resets the Windows networking stack to its default state - If your VPN connects but DNS does not resolve (websites fail but pinging IP addresses works), set your DNS servers manually to your VPN provider's DNS or to a public DNS like 1.1.1.1 or 8.8.8.8 in your network adapter settings
Reinstall the TAP or TUN adapter
OpenVPN-based VPN clients use a virtual network adapter (TAP-Windows or TUN) that can become corrupted:
- Open Device Manager → expand Network adapters
- Look for TAP-Windows Adapter or Wintun. Right-click → Uninstall device (check the box to delete the driver if offered)
- Reinstall your VPN client — it will reinstall the adapter automatically
- If the adapter shows a yellow warning triangle in Device Manager, the driver is corrupted. Uninstall, restart, and reinstall
Check Windows VPN services
Windows VPN connections depend on specific services running:
- Press Win+R, type
services.msc, press Enter - Find and verify these services are running (right-click → Start if stopped):
- Remote Access Connection Manager (RasMan): manages VPN and dial-up connections
- IKE and AuthIP IPsec Keying Modules: required for IKEv2 and IPsec VPNs
- IPsec Policy Agent: required for L2TP/IPsec connections
- Set each to Automatic startup type so they start with Windows
Fix VPN connects but no internet
If the VPN shows connected but you cannot access anything:
- Split tunneling: check if your VPN is set to route all traffic or only specific traffic through the tunnel. If split tunneling is enabled, some traffic bypasses the VPN — this is normal but means only VPN-routed destinations are reachable through the tunnel
- DNS not routing through VPN: even with the tunnel up, DNS queries may go to your ISP's servers which cannot resolve internal addresses. Set your DNS to the VPN's DNS server
- MTU issues: VPN encapsulation adds overhead that can cause packets to be too large. In Command Prompt as admin, run
netsh interface ipv4 set subinterface "YourVPNAdapter" mtu=1400 store=persistentto reduce the MTU - Routing table conflict: run
route printin Command Prompt and check that the VPN's virtual adapter has the correct default gateway. Sometimes two default routes conflict
Corporate VPN troubleshooting
Corporate VPNs (Cisco AnyConnect, GlobalProtect, Pulse Secure, FortiClient) have additional failure points:
- Certificates may need renewing — contact IT if you see certificate errors
- Group Policy may restrict VPN connections on your device. If you recently changed networks or domains, the policy may need to refresh: run
gpupdate /forcein an admin Command Prompt - Multi-factor authentication tokens can expire or desync. Re-enroll your MFA device if one-time codes are being rejected
- Some corporate VPNs require you to be running specific Windows updates or security software. Check with IT for compliance requirements
Remote VPN troubleshooting
If your VPN still will not connect after trying these fixes, Marion Remote Fix can diagnose the problem remotely — checking your VPN configuration, network settings, firewall rules, adapter drivers, and routing tables through a secure remote session.