A VPN can work at home but fail immediately on company, campus, hotel, or airport Wi-Fi. That does not automatically mean the VPN server is down. The local network may restrict ports, protocols, DNS, authentication, or personal VPN usage.
Quick answer
When a VPN is blocked on a managed or public network, first check whether the network requires captive portal login. Then test whether UDP, non-standard ports, DNS, TLS handshake, or firewall policy is blocking the tunnel. On company or school networks, follow the acceptable-use policy and use approved remote-access tools.
Check captive portal first
Hotels, airports, cafes, and campuses often require a browser login or terms confirmation before allowing outbound connections. Turn off the VPN, open a simple web page, complete the portal, and only then reconnect the VPN.
UDP may be blocked
Some VPN protocols and real-time applications depend on UDP. If the network only allows TCP, the VPN may resolve the server but fail to pass traffic. In that case, a TCP-based profile or a more common port may behave differently.
Port and protocol filtering
Managed networks may allow only common ports such as 80, 443, and 53. They may also identify obvious VPN or proxy protocol patterns. If the restriction is protocol-level, switching to another server with the same setup may not help.
DNS and TLS symptoms
Some networks intercept DNS or inspect TLS handshakes. Symptoms include failed server-name resolution, certificate warnings, redirects to local login pages, or handshake errors. Compare the problem with the TLS, SNI, and ALPN VPN handshake guide.
Policy boundaries
Company and campus networks may explicitly restrict personal VPN use. A personal VPN should not be used to bypass workplace security rules, access blocked internal systems, or evade monitoring. Use approved corporate VPN or zero-trust access when working with company resources.
Troubleshooting order
- Verify that normal web browsing works without the VPN.
- Complete captive portal login if required.
- Try a mobile hotspot to compare network behavior.
- Test a TCP or standard-port profile if available.
- Check DNS, TLS, SNI, and routing rules.
- On managed networks, confirm whether personal VPN usage is allowed.
FAQ
Why does the VPN work at home but not at work?
Work networks often have stricter firewall, port, protocol, and security policies than home networks.
Will changing servers always fix it?
No. If the network blocks a protocol or port type, similar servers may fail the same way.
Should I use a personal VPN to bypass company policy?
No. Use approved remote-access systems for work resources.