Plain VPN

VPN Connected but No Internet? Find What Stops Working

简体中文

A VPN can report a successful connection while a browser still fails to resolve a name, reach a destination, or open a page. Start by finding out whether the failure affects one site, one app, or the whole device. That observation gives you a better next step than reinstalling an app or resetting the network.

About 3 min read

VPN connected but no internet? Check what still works

  • Only one website fails. Try two unrelated public sites on the same connection. If they load, note the failing site and its error.
  • Every site and app fails. Check whether the Wi-Fi network still requires you to sign in. Compare the result on another trusted network. Review the VPN app’s protection settings on a personal device, or use your IT team’s approved test on a managed device.
  • Only work sites fail. Leave the work VPN configuration in place, write down the affected app or hostname, and follow the work VPN internal access checklist.

Start with two sites and one app

  1. 01 · Name lookupDoes the name resolve?
  2. 02 · Network pathCan you reach the service?
  3. 03 · App responseDoes the page load?
Three checks to make after the VPN connects.

Choose two unrelated public HTTPS sites and one familiar network app. On the same device and connection, write down which ones work and what error each failure shows. On a personal device where disconnecting is permitted, briefly repeat those harmless checks without the VPN. Use an approved baseline on a managed device or where the VPN is required.

If one site fails, distinguish a name lookup error, a timeout, and a response denying access. If multiple sites fail in one browser but other apps still work, record any browser-specific proxy or encrypted DNS settings. If everything stops, check the device's connection state, any recent VPN reconnect, and whether the network still requires a sign-in.

Let the symptom choose the next check

What you seeWhere to look firstWhat to record
Only name lookups failSystem and browser DNS policyThe failing app and whether a second public name resolves
Public sites work but an internal site failsCorporate DNS, route, or access policyWhich authorised resource fails and when
Every app pauses during reconnectNetwork change, VPN state, and kill switchWhat disconnected and how long recovery took
One site denies accessThe site's own restrictions, account, or service statusIts error and whether another site works

A successful DNS lookup gives you an address to try. The subsequent network path, TLS connection, or web service can still fail. A browser may also use different DNS settings from another app. Avoid substituting a bare IP address in an HTTPS browser test to judge certificate errors. The site may require the correct hostname.

Look for a reconnect or kill-switch event

If the trouble began when the laptop woke up or the phone switched networks, look for a reconnect or protection notice in the VPN app. A kill switch can block traffic while the tunnel is unavailable. Record when the interruption starts and when it clears, and follow the app's normal reconnect guidance. Leave the corporate DNS, routing, and protection configuration in place and send your observations to its administrator.

On Windows, Microsoft's VPN name-resolution documentation explains how a profile may influence DNS. If a name resolves, keep investigating the affected app and destination. If it fails, note whether both the operating system and the browser show a lookup problem. These clues help support reproduce the issue without guessing.

Give support the scope of the failure

Include the OS and app versions, connection time, first error, the affected apps, and what happened to the same target under your approved baseline. Share private resource details only with your organisation's support team. If the failure returns, repeat your original two-site check so the new result can be compared with the first one.

Frequently asked questions

If a new server fixes it, do I know what broke?

You know that changing the path or exit changed the result. The original error and a repeat test are needed to separate a server issue from DNS or the destination.

Why does an internal site fail when public sites still work?

An internal service may require particular DNS settings, routes, and account permissions. Ask its administrator to verify the expected configuration using a resource you can access.

Sources