topic Re: SNX issue with R81.20 Takae 92 in SASE and Remote Access

SNX issue with R81.20 Takae 92

VIKAS1 — Fri, 16 May 2025 09:39:37 GMT

Hi,

We are using ClusterXL with R81.20 and take 92. end user facing issue while connecting Mobile access agent , agent version -800.007.049 and SNX version is 80008409. and we are using JAVA version as per checkpoint recommended.

when we uninstall the agent and trying to login , it will get connect.

is anyone face same issue or is there any SK for it.

Re: SNX issue with R81.20 Takae 92

PhoneBoy — Fri, 16 May 2025 21:09:51 GMT

This statement is unclear: "when we uninstall the agent and trying to login , it will get connect."
Please describe the step-by-step process you are following in detail with screenshots (mask any sensitive data), particularly error messages.

Re: SNX issue with R81.20 Takae 92

the_rock — Sun, 18 May 2025 14:35:28 GMT

Do you have an actual error message?

Andy

Re: SNX issue with R81.20 Takae 92

the_rock — Mon, 19 May 2025 21:10:01 GMT

Might be worth install jumbo 99, its recommended, plus lots of VPN fixes.

Andy

Re: SNX issue with R81.20 Takae 92

VIKAS1 — Tue, 20 May 2025 04:21:42 GMT

Hi Rock,

I have reviewed JHF 99, but before proceeding with any plans, we are coordinating with TAC to get confirmation.

We had connected with TAC earlier, and at that time they recommended installing JHF 92 to resolve the issue. However, the issue still persists.

Re: SNX issue with R81.20 Takae 92

VIKAS1 — Tue, 20 May 2025 04:54:34 GMT

Hi,

We are currently experiencing an issue with the Mobile Access Agent on our Check Point ClusterXL environment running R81.20 (Take 92).

Affected components:

Mobile Access Agent version: 800.007.049
SNX version: 80008409
Java version: As per Check Point recommended version
End users are currently unable to connect using the installed Mobile Access Agent. However, if the agent is uninstalled and then reinstalled, users are able to connect successfully via the Mobile Access Agent.
This behavior suggests a potential issue with the locally installed agent or its configuration. We would appreciate any guidance or recommendations to help identify and resolve the root cause.