Windows VPN Not Connecting: Basic Troubleshooting Checklist
Basic Windows VPN troubleshooting when a connection cannot be established.
First confirm ordinary internet access
Disconnect the VPN and try several normal websites. If they also fail, the problem is the local connection rather than the VPN. Reconnect to Wi-Fi, complete any hotel or airport login page, or restore mobile data before testing the VPN again.
Why a VPN can be connected while browsing fails
- DNS resolution: the device cannot translate a website name into an address.
- Routing: the tunnel exists but traffic is not reaching the expected destination.
- Captive portal: the local network still requires a browser login.
- Network transition: Wi-Fi or mobile data changed after the tunnel was created.
- Temporary destination filtering or outage: one website or service may be unavailable even though the VPN itself is connected.
Test more than one destination
Do not use a single website as the only test. Try a few unrelated sites and, if available, a public-IP check. If one site fails but others work, the issue is probably specific to that destination rather than general internet connectivity.
Check whether the public IP changed
A public-IP check can confirm whether ordinary web traffic appears to be exiting through the VPN path. Use the How to Check Your VPN IP Address guide for a simple before-and-after test.
If names fail but direct connectivity works
That pattern can indicate a DNS problem. Avoid manually forcing random DNS settings as a first reaction because that can create a second problem. Restart the connection cleanly and use the VPN client’s intended configuration before experimenting with advanced network settings.
Captive portals are a special case
Hotels, airports and cafés often permit only limited traffic until you open a browser and accept terms, enter a room number, or complete another login step. If the VPN starts before that process is complete, the local network may block the tunnel or block general internet access behind it. Finish the network login first, confirm ordinary browsing, and then reconnect the VPN.
Use a clean recovery order
- Disconnect the VPN.
- Confirm the local network can browse normally.
- Complete any Wi-Fi login page.
- Reconnect the VPN once.
- Test several unrelated destinations.
- Check the public IP.
If this restores access, there is usually no reason to reinstall the client. If the tunnel repeatedly fails after this sequence, move to connection or disconnect troubleshooting.
Frequently Asked Questions
Why does my VPN say connected when nothing loads?
The tunnel can exist even if DNS, routing, or the underlying internet connection is not usable beyond it.
Can a hotel login page cause this?
Yes. Some networks require you to accept terms or authenticate before general internet traffic is allowed.
Is this the same as a VPN that will not connect?
No. “Will not connect” means tunnel establishment fails. “Connected but no internet” begins after the tunnel is already up.