GlobalProtect shows Connected, but the intranet times out and internal applications do not load. Start with one application, its expected IP address, and its actual service port. Follow the same connection from Windows to the GlobalProtect gateway, the PAN-OS security policy, and the destination network. This guide assumes a Windows 11 endpoint connected to an external GlobalProtect gateway on a PAN-OS firewall.
1. Compare access by IP and hostname
Use PowerShell while connected. Replace the example IP, hostname, and port with those of an application the user is authorized to access.
Test-NetConnection -ComputerName 10.20.30.40 -Port 443 -InformationLevel Detailed
Resolve-DnsName -Name payroll.corp.example -Type A -DnsOnly
Test-NetConnection -ComputerName payroll.corp.example -Port 443 -InformationLevel Detailed
Record the test time and time zone, selected gateway, assigned tunnel IP, expected destination, and application port. Compare the result with a working user on the same gateway and client settings profile when possible.
| Result | Where to look first |
|---|---|
| TCP by IP succeeds, but the name fails or resolves to the wrong address | DNS policy, resolver assignment, and internal DNS records |
| TCP by IP fails | Windows route, gateway forwarding, PAN-OS policy, server listener, and return path |
| TCP by name succeeds, but the application fails | TLS, browser proxy, application authentication, or server response |
| One subnet fails while another works | Access route for the failed subnet and policy for that destination |
Read TcpTestSucceeded and RemoteAddress. A successful TCP handshake confirms that the port is reachable from that test process. Check the application itself if it uses its own proxy or is affected by application-based split tunneling.
2. Verify the Windows route and the applied GlobalProtect profile
Find-NetRoute -RemoteIPAddress 10.20.30.40
Get-NetIPConfiguration
Review the selected interface, source address, and destination prefix. If the route points to Wi-Fi or Ethernet when the destination should use the VPN, inspect the client settings profile applied by the connected gateway. On the firewall, go to Network → GlobalProtect → Gateways → gateway → Agent → Client Settings. Under Split Tunnel → Access Route, compare the included and excluded prefixes with the failing destination. Verify the profile’s selection criteria for the affected user or endpoint before editing its routes.
If the home network overlaps the corporate network, Windows can select the local path, especially when its route is more specific. Compare the selected prefix with the expected VPN prefix and retest from an approved network with a different address range. If the deployment uses domain- or application-based split tunneling, reproduce the failure in the actual application as well as in PowerShell.
3. Check internal DNS separately
Get-DnsClientServerAddress -AddressFamily IPv4
Find-NetRoute -RemoteIPAddress 10.20.0.53
Resolve-DnsName -Name payroll.corp.example -Server 10.20.0.53 -Type A -DnsOnly
The example resolver is 10.20.0.53. Compare the direct query with the default lookup from step 1.
- The explicit query works and the default lookup fails. Verify the DNS servers assigned through the gateway’s client settings under Network Services. If split DNS is configured, compare the portal app settings and gateway domain rules for the affected name.
- The explicit query times out. Verify the selected route to the resolver and check policy or server logs for DNS traffic from the tunnel IP. Review UDP and TCP 53 where applicable.
- The resolver answers with an unexpected address. Check the internal record and DNS view. If the application publishes an AAAA record, verify the IPv6 answer and path as well.
A direct query tests the specified resolver. Repeat the default lookup after any correction, then test the application from the affected client.
4. Match the test to PAN-OS Traffic logs
Open Monitor → Logs → Traffic. Filter for the assigned tunnel IP, destination IP, application port, and the test time. For example, with a tunnel IP of 10.250.10.25:
(addr.src in 10.250.10.25) and (addr.dst in 10.20.30.40) and (port.dst eq 443)
Open the matching entry and compare the source zone, destination zone, rule, action, and egress interface with the expected traffic path. The source zone normally follows the tunnel interface’s zone assignment. For an allowed session, inspect Bytes Sent, Bytes Received, and Session End Reason.
| Finding | Next check |
|---|---|
| Deny or drop | Verify the tunnel source zone, destination zone, user or group match, and application and service in the intended Security rule. |
| Allow, with outbound bytes and no received bytes | Check the server listener, host firewall, and return route toward the GlobalProtect client pool. If source NAT applies, trace the translated address seen by the server. |
| Allow, with bytes in both directions | Inspect the application, TLS, proxy, and any related security logs. |
| No matching entry | Check the timestamp, gateway or virtual system, and rule logging configuration. A rule configured for session-end logging may log the connection only after it closes. |
If a route change is suspected, check the PAN-OS virtual router or logical router that handles the tunnel traffic. A valid Windows route only establishes where the endpoint sends its traffic. The gateway still needs a valid path to the server, and the server network needs a return path through the expected firewall.
Worked example: Only one internal subnet is unreachable
A remote employee connects successfully and can reach the corporate DNS server. The payroll hostname resolves to 10.20.30.40, but TCP 443 fails. Windows selects the local Wi-Fi interface for that IP and the gateway shows no corresponding test session. An engineer checks the applied gateway profile and confirms that the newly added payroll subnet is missing from the approved split-tunnel access routes.
After adding the approved prefix to that profile through the normal change process, the engineer reconnects the client. Windows now selects the GlobalProtect path. The new TCP test succeeds, PAN-OS logs the expected Security rule, and the employee signs in using the original hostname. The engineer also verifies that access to a separate restricted subnet remains denied.