Firewall Support Center

GlobalProtect Connects but Large Transfers Stall: Check the Path MTU

A GlobalProtect client can resolve the server and open the application. A large transfer stalls while a small response completes. That pattern makes the path MTU worth checking alongside application timeouts, loss, and tunnel transport.

Reproduce consistently. Use an approved application endpoint and compare a small and large transfer on the same client. Repeat on a known-good network or client and record the gateway and VPN transport. Collect the GlobalProtect client logs and correlate the timestamps with firewall or application observations.

For an approved destination that replies to ICMP, compare IPv4 probes with different payload sizes:

ping -4 -f -l 1200 10.20.30.40
ping -4 -f -l 1350 10.20.30.40

These values are examples. A missing response can reflect ICMP policy or loss. Compare repeatable results and look for packet evidence such as fragmentation-needed messages or repeated retransmissions before changing settings.

Worked example. The same transfer stalls only on one uplink, and measurements support a smaller effective path MTU there. The administrator pilots a supported adjustment for the affected deployment and repeats the large transfer. Track completion and retransmissions, and confirm previously working paths still behave as expected.

See Palo Alto Networks’ GlobalProtect MTU troubleshooting note and the GlobalProtect connectivity guide.