Knowledge Base / Network / Firewall and VPN Escalation Steps
Problem
Practical checks for firewall and VPN escalation steps. Follow the safe steps below and contact your support team if the issue continues.
These are general troubleshooting checks, not a confirmed diagnosis. Follow your organization's procedures and stop if a step could risk data, safety, or managed equipment.
Symptoms to check
- Users cannot connect to the VPN, see repeated login prompts, or lose traffic after connecting.
- The issue may affect one user, several users, or a whole office depending on policy or infrastructure changes.
Possible causes
- Firewall policy drift, VPN profile problems, certificate errors, or account authorization issues may block access.
- Client software or network restrictions can also cause repeated connection failures.
Resolution
- Confirm whether the issue is isolated to one user or all users. Check the current VPN status, client version, login username, and whether the user is on the correct network or device.
- Collect the exact error code, connection time, and whether the user can still reach internal services without the VPN. This helps the support or network team distinguish access problems from general connectivity problems.
- Verify the VPN profile is up to date and that the user has permission to access the required resource. Remove any outdated or duplicate connection profiles if the organization allows it.
- If several users are affected, review any recent firewall change, certificate update, or gateway outage. If the issue is tied to a policy update, it may require a network or security escalation.
- Escalate to the network or security team with the scope, error details, timestamp, and any recent changes to the VPN or firewall environment.
Prevention and preparation
- Keep VPN clients and firewall rules reviewed and under change control.
- Document approved remote-access policies and known-good connection steps for staff.
Related guides
Still not fixed? Log a support request and include the exact error, who or what is affected, and the steps you already tried. Never include passwords or verification codes.
Submit a ticketLast reviewed: October 2026