Remote Access VPN Issues
Cannot connect to VPN: verify internet connectivity first (VPN requires internet access). Verify VPN gateway IP or hostname is correct. Check firewall: UDP 500/4500 (IPsec), TCP 443 (SSL VPN) must be permitted. Check authentication credentials (wrong username/password, expired password, locked account). Certificate expired or not trusted (for certificate-based auth).
Connected but cannot reach internal resources: check split tunneling configuration — if enabled, ensure corporate subnets are routed through the tunnel. Check DNS: VPN client may not be using internal DNS. Verify the VPN-assigned IP is in the correct IP range and has routing to internal networks. Check firewall rules on the VPN gateway — inbound traffic from VPN pool to internal servers.
VPN disconnects intermittently: NAT traversal (NAT-T) issues on UDP 4500 — some NAT devices drop idle UDP sessions. Enable NAT-T keepalives. ISP-level DPI blocking VPN traffic. DPD (Dead Peer Detection) — if enabled and the connection is dropped too aggressively, reduce DPD timeout.
Site-to-Site VPN Issues
Phase 1 (IKE) failure: IKE negotiation fails because parameters don't match. Check: both sides must have identical IKE version, encryption algorithm, hash, DH group, lifetime, and authentication method. Any mismatch causes Phase 1 to fail — the tunnel never forms.
Phase 2 (IPsec) failure: Phase 1 succeeds but Phase 2 fails. Check: transform set (encryption, hash) must match on both sides. Interesting traffic (proxy IDs / traffic selectors) must match — both sides must agree on what traffic is 'interesting' and should go through the tunnel. Asymmetric interesting traffic definitions prevent the tunnel from forming.
Tunnel up but no traffic: Phase 1 and 2 succeed, but traffic doesn't flow. Check routing: is there a route pointing traffic to the VPN tunnel interface? Check NAT: is NAT translating the tunnel traffic before it reaches the VPN? NAT exemption rules are needed to prevent NAT from modifying VPN traffic.