A VPN status showing connected means a tunnel or session was established. It does not guarantee that every internal application, route, DNS name, or permission is working.
Narrow down what fails
Record the application or resource name and exact error. Check whether public internet access still works and whether more than one internal resource fails. Note whether colleagues using the same approved VPN can reach the resource.
Confirm you selected the correct company profile and completed the required authentication. Record the device, location, connection type, and time of the failure. Avoid repeatedly approving unexpected authentication prompts.
Common areas for administrator review
- Internal name resolution through the intended DNS servers.
- Routes to the required networks and the approved split-tunnel policy.
- Access permissions for your user or device.
- An overlap between home-network and company-network address ranges.
- Availability of the internal service itself.
An IP overlap can cause a device to send traffic to the wrong local network. Do not change home-router addressing or the company's VPN routes without a coordinated plan.
Escalate without weakening protection
Send support the resource name, error, VPN profile, and test results. Do not expose the internal service publicly, turn off the firewall, or install another VPN as a workaround. Your administrator can distinguish a tunnel problem from routing, DNS, authorization, or application failure and choose the appropriate repair.
Get help with your network
For an existing service issue, open an AvrinTech support ticket. For an assessment or planned improvement, request a scoped proposal and review our networking services. Work, coverage, and response targets depend on your agreement.
