VPN works everywhere except at home, since the new internet provider
Some ISPs (low-cost cable, mobile, Starlink) put you behind Carrier-Grade NAT. Inbound traffic and some VPN protocols stop working reliably.
Try this first
- 1Check public IP on a site like ip.nl and compare with the WAN address on the router. If they differ and the WAN IP starts with 100.64.x.x, you are behind CGNAT.
- 2Call the ISP and request a public IPv4. With some it is a free toggle, with others a small monthly fee. Ask explicitly, not "VPN broken".
- 3No public IP available, switch to a VPN protocol that handles NAT traversal better. WireGuard and IKEv2 typically beat classic IPsec behind CGNAT.
- 4IPv6 as alternative, if your VPN server has an IPv6 endpoint. CGNAT only affects IPv4, IPv6 is end-to-end.
- 5Temporary fallback: hotspot via phone (4G/5G is often CGNAT too, but different paths), or a Tailscale/ZTNA overlay that traverses CGNAT.
When to bring us in
For a fully remote team you do not want one-by-one ISP calls. A ZTNA overlay (Tailscale, Cloudflare Access) fixes this structurally. Ask us for a comparison.
See also
- VPN will not connect or keeps droppingTwo main causes: your home internet or the VPN server. One quick test separates them.
- VPN connects but corporate folders are unreachableConnection says "green" but your network drives will not open. Almost always a DNS or routing issue.
- Home PC slow on VPN, fast at the officeThree suspects: home internet, VPN server limits, or routing that takes a long detour.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.