VPN connects but cannot reach internal file shares

Minimal guidance for messy support realities.

Scenario

The VPN client shows connected, but mapped drives and UNC paths do not open. Internet access continues to work normally.

Recommended Resolution Path

  1. Check the assigned VPN IP and confirm split-tunnel routes include the file server subnet.
  2. Ping the file server by IP and by hostname to determine whether the issue is routing or DNS.
  3. Flush DNS and renew the tunnel if internal name resolution is stale.
  4. Verify the firewall on the file server allows SMB from the VPN address pool.

Technician Notes

Confirm the business impact, document the root cause, and capture any preventative follow-up in the PSA or client knowledge base.