VPN Will Not Connect: A Safe Troubleshooting Guide for Remote Workers
VPN Will Not Connect: A Safe Troubleshooting Guide for Remote Workers
A virtual private network (VPN) creates an approved path to private company resources. A VPN failure may involve the local internet connection, the VPN service, credentials or multifactor authentication (MFA), the device clock, or a managed security policy. Do not remove and recreate a company VPN unless IT provides instructions.
Start with ordinary internet access
Disconnect the VPN only if policy allows, then open two trusted public websites. If they do not load, solve the underlying internet problem first. Test another permitted network if available. Hotel, airport, and café networks may require a browser sign-in page before the VPN can connect; complete it only after confirming the network is legitimate.
Avoid sensitive work on public Wi-Fi. Use an employer-approved hotspot when possible. Never accept unexpected certificate warnings to “make it work.” A certificate warning can indicate the wrong server, an interception attempt, or an expired configuration.
Check the basics
- Restart the computer normally.
- Confirm the date, time, and time zone are correct and set automatically. Authentication can fail when the clock is wrong.
- Open the organization’s approved VPN application or, for a built-in connection, the operating system’s VPN settings.
- Select the exact profile supplied by IT. Do not guess a server address or VPN type.
- Enter your current work credentials. Approve an MFA request only if you initiated the login and the displayed location or details make sense.
If you receive repeated MFA prompts you did not initiate, deny them and contact your security team. Never read an MFA code or password to an unsolicited caller.
On Windows, VPN connections are under Settings > Network & internet > VPN. On macOS, managed VPN configurations normally appear under System Settings > VPN or are controlled by the organization’s VPN app. The exact layout varies by operating-system version and management policy.
Interpret common symptoms
- “Authentication failed” or “access denied”: verify the username format, password status, and MFA. Your account may be locked or not assigned to the VPN.
- “Server not found” or timeout: confirm normal internet works, then note the server/profile name and time. The service may be unavailable or blocked on the current network.
- Connects, but internal resources fail: record which resource, hostname, or application fails. Do not change DNS, routes, or proxy settings yourself.
- Internet stops after connection: this can be intentional if all traffic must pass through the company. Report it rather than disabling security settings.
- Connection drops during sleep or network changes: reconnect after the device wakes or after switching Wi-Fi. If it repeats, gather logs through the approved support process.
Do not disable the firewall, antivirus, endpoint agent, or router security; do not install a consumer “free VPN” alongside the corporate client. Competing VPN and filtering products can conflict and may expose business data.
Preserve useful evidence
Capture the full error message, error number, VPN application name and version, operating system, network type, and exact time. Note whether coworkers are affected and whether the VPN works on another approved connection. If the app has Collect diagnostics or Export logs, use it only as directed; logs can contain company addresses and should not be posted publicly.
Contact support immediately after repeated unexpected MFA prompts, certificate warnings, suspected account compromise, or a VPN profile that changed without explanation. Support may need to check account assignment, certificate validity, device compliance, service status, or firewall logs.