Checkpoint Endpoint Security VPN Client not working anymore on Windows 11

[jonas_w]

Hello!

Until today, Checkpoint Endpoint Security VPN worked without issues. Today, the VPN Client stopped working.

• The VPN simply displays "No security policy is configured." as shown in the attached screenshot.
• My VPN profile isnt present anymore, and the client won't allow me to add new profiles. The wizard won't let me click next after entering the IP address of the gateway.

Further investigation:

• The windows service "Check Point Endpoint Security VPN" keeps terminating and restarting. I have a couple thousand error messages in Windows Event Viewer with the following text: "The Check Point Endpoint Security VPN service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service."
• I have found the following fragment in trac.log:

... more messages that indicate normal startup (?)

[ 28300 29032][18 Nov 18:29:23][TR_CL2SRV_X] TR_CL2SRV_X::RegisterCb: Registered cb b96e10 for message 1019
[ 28300 29032][18 Nov 18:29:23][TR_CL2SRV_X] TR_CL2SRV_X::RegisterCb: Registered cb bf16c0 for message 1016
[ 28300 29032][18 Nov 18:29:23][TR_CL2SRV_X] TR_CL2SRV_X::RegisterCb: Registered cb befa70 for message 1017
[ 28300 29032][18 Nov 18:29:23][TR_CL2SRV_X] TR_CL2SRV_X::RegisterCb: Registered cb bda450 for message 1020
[ 28300 29032][18 Nov 18:29:23][TR_CL2SRV_X] TR_CL2SRV_X::RegisterCb: Registered cb b75fd0 for message 0
[ 28300 29032][18 Nov 18:29:23][TR_CL2SRV_X] TR_CL2SRV_X::RegisterCb: Registered cb b754c0 for message 1
[ 28300 29032][18 Nov 18:29:23][TrComInf] TrComInf::TrComInfInit: __start__ 18:29:23.384
[ 28300 29032][18 Nov 18:29:23][TrComInf] TrComInf::TrComInf::TrComInfInit: enter...
[ 28300 29032][18 Nov 18:29:23][messaging] messaging::add_msg: added a new cb: msg - 1
[ 28300 29032][18 Nov 18:29:23][messaging] messaging::add_msg: added a new cb: msg - 2
[ 28300 29032][18 Nov 18:29:23][tcpserver] TcpMultiPipe::socket_init: Created m_serverfd: 0x338 socket
[ 28300 29032][18 Nov 18:29:23][tcpserver] TcpMultiPipe::socket_init: setsockopt - ok!
[ 28300 29032][18 Nov 18:29:23][tcpserver] TcpMultiPipe::socket_init: ioctlsocket - ok!
[ 28300 29032][18 Nov 18:29:23][tcpserver] TcpMultiPipe::socket_init: [SEVERE]: Failed to bind to socket: Unknown Winsock error (10013)
[ 28300 29032][18 Nov 18:29:23][tcpserver] TcpMultiPipe::pipe_if_server_init: [SEVERE]: Failed to initialize SOCKET
[ 28300 29032][18 Nov 18:29:23][messaging] messaging::init: Failed to initialize pipe
[ 28300 29032][18 Nov 18:29:23][TrComInf] TrComInf::TrComInf::TrComInfInit: Failed to init messaging
[ 28300 29032][18 Nov 18:29:23][TrComInf] TrComInf::TrComInfInit: __end__ 18:29:23.384. Total time - 0 milliseconds
[ 28300 29032][18 Nov 18:29:23][TR_OVERSITE] TR_OVERSITE::Create: Destroying TrOversite ...
[ 28300 29032][18 Nov 18:29:23][TR_FIREWALL] UploadLogsComponent::Inst: create UploadLogsComponent instance
[ 28300 29032][18 Nov 18:29:23][TR_FIREWALL] UploadLogsComponent::FlushBufferToFile: entering
[ 28300 29032][18 Nov 18:29:23][TR_FIREWALL] UploadLogsComponent::FlushBufferToFile: m_logConf is NULL
[ 28300 29032][18 Nov 18:29:23][CONFIG_MANAGER] ConfigurationManager::destroy: __start__ 18:29:23.384
[ 28300 29032][18 Nov 18:29:23][CONFIG_MANAGER] ConfigurationManager::destroy: delete mInst
[ 28300 29032][18 Nov 18:29:23][CONFIG_MANAGER] ConfigurationManager::~ConfigurationManager: __start__ 18:29:23.384
[ 28300 29032][18 Nov 18:29:23][CONFIG_MANAGER] ConfigurationManager::saveToFile()
[ 28300 29032][18 Nov 18:29:23][XmlWrapper] XmlDocument::XmlDocument: inside
[ 28300 29032][18 Nov 18:29:23][XmlWrapper] XmlDocument::SaveString: inside
[ 28300 29032][18 Nov 18:29:23][CONFIG_MANAGER] ConfigurationManager::saveToFile(): got xml: 
<CONFIGURATION></CONFIGURATION>

[ 28300 29032][18 Nov 18:29:23][CONFIG_MANAGER] OBSCURE_FILE return value 1, because it is Default variable. Scope: site NULL, gw NULL ,user USER 
[ 28300 29032][18 Nov 18:29:23][CONFIG_MANAGER] Updated trac.conf.bak
[ 28300 29032][18 Nov 18:29:23][CONFIG_MANAGER] Updated trac.conf

... more messages indicating service shutdown

The message "[SEVERE]: Failed to bind to socket: Unknown Winsock error (10013)" is the only error I can find in that file. I have truncated the file, since I am not sure what messages in this log contain sensitive data. If the full log is needed, that can be arranged.

What does it mean? What can I do to fix this issue?

Thank you and best regards,

Jonas

---

OS: Windows 11 23H2

Version: VPN E86.80 Build 986104309

Exact version/JHF take level of gateway: I don't know what that is. I think it might not be relevant to the issue.

[PhoneBoy]

It's a known issue.
First, you need to be on the latest version E88.60 (latest client release): https://support.checkpoint.com/results/sk/sk182468
Second, you will need to edit trac.config (located in C:\Program Files (X86\CheckPoint\Endpoint Connect) and restart the VPN service per: https://support.checkpoint.com/results/sk/sk182749 

We do plan to fix this in an upcoming version.

[HengL_12341234]

I updated trac.config,and version is latest client release,but i not found $FWDIR/conf/trac_client_1.ttm file in my pc

[PhoneBoy]

That file is for a gateway and is not relevant on a client.
For a client, you need to edit trac.config file in the location I described above.
The SK explains the exact change you need to make.

[HengL_12341234]

when i click VPN Options Will popup error "Check Point Mobile Connectivity with the VPN service is lost",
and trac.log errors also is "Failed to bind to socket: Unknown Winsock error (10013)"

[piterskikh]

HengL_12341234 The same behavior is observed in version E88.60. I also cannot find the files and receive the same error  "Check Point Mobile Connectivity with the VPN service is lost". The article is not detailed. Which version was being referred to? When will the corrected program be released? Please provide at least an approximate timeline.

[BrunoRoque]

I have the same problem, I even get a Blue Screen with the error Kernel_Mode_Heap_Corruption passing sometime.

[Chris_Atkinson]

Please note per sk115192 client support for Win11 24H2 is not yet GA.

An updated client version is coming soon.

[the_rock]

I heard all these issues should be fixed with E89 client, but not sure when thats coming out. I hope either next month or latest January...

Andy

[jonas_w · Accepted solution]

For my case, it turned out it was an incompatibility between some ASUS services and the Checkpoint VPN service. I also got the heap corruption blue screens. I have an Asus Zephyrus G16 2024 laptop. I think both are trying to open a socket on the same port or something, and when the Checkpoint Service is trying to start while the ASUS services are already running, it crashes continuously.

Disabling ASUS services fixed it. I have them disabled usually and use third party software for laptop management instead. I believe some sort of update enabled them.

[the_rock]

That seems to be issue with probably most vendors' VPN clients, its usually something to do with 3rd party software installed on the laptop.

Andy