How does L2TP VPN affect Mobile desktop Client?

[NorthernNetGuy]

We updated the Clusters L2TP certificate due to changing the name of the cluster object. Now our users using Checkpoint Desktop Mobile client can't access our internal resources without deleting their old VPN profile and creating it again, with the same information (cluster object name not referenced). They can successfully authenticate still, but receive frequent disconnects until they do this profile recreate. We use user credentials for authentication on it

I thought the Mobile access blade desktop client used SSL vpn and wouldn't be affected by changes done to the IPSec VPN blade and its L2TP cert?

[G_W_Albrecht]

Seems rather a strange issue: Checkpoint Desktop Mobile client can't access our internal resources, but can successfully authenticate still, but receive frequent disconnects ?

What reason is given in logs for the frequent disconnects ? Either authentication succeeds or not - everything else is a matter of access rules matching.

[NorthernNetGuy · Accepted solution]

I ended up opening a ticket with support.

It looks like our NAT traversal was set to an unusual port after we disabled and re-enabled the IPSec VPN blade. We changed back to the regular IKE_NAT_TRAVERSAL port 4500, and the issue seems to be resolved.