topic Re: always-connect for standalone vpn client in General Topics

always-connect for standalone vpn client

MiniNinja — Tue, 15 Jul 2025 06:19:19 GMT

The standalone VPN client checkpoint has an always-connect option.

There are 2 VPN gateways (R81.20 take 105) managed by the same SMS (R81.20 take 105).

Employees of the company are connected to 1, and contractors to 2.

For 1 gateway, the always-connect option must be enabled and prohibit its modification.

While for 2 gateways, need to disable this option.

What I've already tried:

1) On 1 gateway in trac_client_1.ttm set true for neo_always_connected, install policy and recreate the site on the client.

2) In global properties under Remote Access -> Endpoint Connect, under connectivity settings choose connect mode: Always connected.

On gateway 2, in trac_client_1.ttm set false for neo_always_connected, install a policy, and recreate the site on the client.

3) In global properties under Remote Access -> Endpoint Connect, under connectivity settings choose connect mode: Always connected.

On gateway 2, in trac_client_1.ttm set false for neo_always_connected, install a policy, and recreate the site on the client.

On gateway 1, in trac_client_1.ttm set true for neo_always_connected, install a policy, and recreate the site on the client.

I tried using the VPN client E88 and E89, the result is identical.

Re: always-connect for standalone vpn client

G_W_Albrecht — Tue, 15 Jul 2025 08:43:11 GMT

I would not configure anything in Global Properties if i want a different behaviour for each GW !

Re: always-connect for standalone vpn client

MiniNinja — Tue, 15 Jul 2025 08:52:31 GMT

The above are 3 options that I tried, including the option to change the settings in the file for only one gateway, but it doesn't work.

1) On 1 gateway in trac_client_1.ttm set true for neo_always_connected, install policy and recreate the site on the client.

Re: always-connect for standalone vpn client

G_W_Albrecht — Tue, 15 Jul 2025 09:14:01 GMT

Open an SR# with CP TAC would be the best option! I still do not understand why you are setting Global Properties: Your option 1 will not change anything for GW2, in option 2 it could be that Global Properties override the GW2 settings and the same is true for option 3!

Re: always-connect for standalone vpn client

MiniNinja — Tue, 15 Jul 2025 09:27:54 GMT

These are my ideas that came to mind after reading the documentation and all the SK I found.
I just described what I tried and it doesn't work.

Re: always-connect for standalone vpn client

G_W_Albrecht — Tue, 15 Jul 2025 10:37:07 GMT

Can not work: In global properties under Remote Access -> Endpoint Connect, under connectivity settings choose connect mode: Always connected. will overide the ttm.

Please read again what you wrote: Option 1 makes no sense at all as it does not configure anything for GW2, and option 2 + 3 has In global properties under Remote Access -> Endpoint Connect, under connectivity settings choose connect mode: Always connected.

@PhoneBoy can we move this to the correct corner 😉