Firewall Support Center

VPN Connects but Some Websites Fail: MTU and MSS Troubleshooting

Investigate VPN connections that pass small packets but stall on larger transfers with controlled MTU tests and packet evidence.

Inner packetApplication data plus IP and transport headers
VPN encapsulationAdditional headers increase the outer packet size
Path bottleneckPacket must fit the next-hop MTU or trigger discovery
Illustrative troubleshooting view · Firewall Support Center

Recognize the pattern

A VPN can authenticate successfully while a file transfer stalls or a particular website never finishes loading. When small transactions work and larger ones fail, add path MTU to the investigation. DNS errors, TLS inspection, and server problems can produce similar symptoms, so first identify the exact destination and failure stage.

MTU and MSS describe different limits

MTU is an interface or path packet-size limit. TCP MSS describes the TCP payload size advertised by an endpoint during connection setup. VPN encapsulation adds overhead, and the amount varies with the tunnel and transport. An MSS change affects TCP. UDP and other protocols require their own analysis.

Measure from the affected client

ping -4 -f -l 1372 10.40.20.50
ping -4 -f -l 1300 10.40.20.50
Test-NetConnection 10.40.20.50 -Port 443

Interpret the Windows test

Use a destination you administer that responds to ICMP. In these Windows IPv4 examples, -l sets the ICMP data length and -f requests the Don’t Fragment flag. With ordinary 20-byte IPv4 and 8-byte ICMP headers, 1372 bytes of data produces a 1400-byte inner IP packet. A successful result establishes that size for this test path. A timeout does not identify MTU as the cause.

Find a repeatable boundary

Increase or decrease the data length around a working value and record the largest consistently successful probe. Repeat on the VPN and on a known-good path. Do not assume an ICMP path exactly reproduces every application path, especially with split tunneling, IPv6, load balancing, or different destinations. Preserve the route and destination used for each measurement.

Look for supporting packet evidence

Capture the failing connection and look for repeated transmissions, missing acknowledgments, and ICMP fragmentation-needed or IPv6 Packet Too Big messages. For TCP, inspect the MSS options in the SYN and SYN-ACK. Identify the first point at which a larger packet disappears. A packet capture from only the client cannot establish what every intermediate device did.

Choose a scoped correction

Correct an inaccurate tunnel MTU, an inappropriate TCP MSS setting, or filtering that prevents required path-discovery messages. GlobalProtect exposes a connection MTU setting whose supported range is documented by Palo Alto. Choose a value from measurements and version-specific guidance. Preserve the original setting and apply a controlled change to the affected population.

Validate more than a ping

TestExpected evidence
Small and large probesRepeatable behavior at the measured packet sizes
Original website or uploadThe previously failing operation completes
TCP handshakeMSS values are consistent with the intended configuration
Other applicationsNo new failure appears on a representative sample

Document the resolved path

Record the client OS, VPN client and gateway versions, destination, measured sizes, packet captures, and exact change. Retest after the next tunnel or ISP change. The effective path can change even when the endpoint configuration remains the same.

Official references

Microsoft ping reference

GlobalProtect connection MTU settings