GlobalProtect clients experiencing latency delays

[Farzana]

Hello,

Clients who are connected via GlobalProtect VPN are experiencing slowness with all their traffic traversing the VPN (ie.. Internet and Server access traffic).

The latency is between 200-400ms for all the traffic regardless of whether its Internet based (to google) or server based (to our corporate servers).

Can you suggest any troubleshooting steps for this? Any relevant article to check?

Thanks in advance.

[Raido_Rattameister · Accepted solution]

In GlobalProtect client, Details tab.

Check if protocol is SSL or IPSec.

If it is SSL then check if you permit udp 4501 towards GlobalProtect gateway.

Also check that you have "Enable IPSec" checked in GlobalProtect gateway config (Tunnel Settings tab).

[jdprovine]

@Raido_Rattameister

So you mean to permit udp 4501 in to the firewall using a security policy permiting it?  I have a rule coming in to the firewall for the global protect client  that has service any and I still get complaints from users that it still too slow.

I looked in network/interfaces/tunnel and I don't see a place in enable ipsec but I do see it enabled when I go to the globalprotect gateway configuration

[Raido_Rattameister]

If you run GlobalProtect on your untrust interface and you don't have block any-any rule added then last interzone-default will permit from untrust to untrust 4501.

If you run GlobalProtect gateway on loopback and then you need to NAT udp 4501 to this loopback.

GlobalProtect agent will try IPSec 3 times and then falls back to SSL.

In case SSL it is TCP inside TCP (tcp meltdown and other issues can occure).

Enable IPSec is in firewall.

[Raido_Rattameister]

If agent view shows IPSec then issue is somewhere else.

[jdprovine]

@Raido_Rattameister

Yes I have IPSEC enabled in the location in your screenshot.  I am using the SSL protocol to connect.  I must add I did not do the original configuration of the VPN's I have got them to work and now I am working at getting them to work as efficiently as I can.

I didn't find any NATTING concerning the loopbacks used for the VPN's

[Raido_Rattameister]

If GP agent shows SSL as protocol it can't connect with IPSec.

Go to Monitor > Traffic and use filter below.

( port.dst eq 4501 )

Do you see it being blocked?

[jdprovine]

@Raido_Rattameister

Port 4501 is not being blocked for legitimate traffic to the loopback for the VPN

[Raido_Rattameister]

Earlier you mentioned you saw no natting but now you mention that GP runs on loopback.

If it runs on loopback there must be DNAT in place.

[jdprovine]

@Raido_Rattameister

Good point I will check again on the natting

[Remo]

@Raido_Rattameister

I also run different portals/gateways on loopbackinterfaces ... but I do not NAT at all in this case. All the loopbacks simply have public IPs so there is no need for DNAT

[Raido_Rattameister]

True it can use external IP but if agent connects overr SSL then most likely it is either Security Policy or NAT that is not configured correctly.

In some rare cases source network but quite rare nowadays.

[dejesusv]

Hi there! I know this thread is older...but how do you create a DNAT for 4501 AND 443?

For example, I have gateway configured with x.x.x.x:7000

I have a DNAT that forwards 7000 to 443.  How do I get it working with 4501? reason I ask is because I want my tunnel to use IPSEC rather than SSL.

Thank you!!