Posted on 8 November 2012 | 4 responses
Checkpoint Endpoint Connect E75.01 is the only native client for 10.8 as it is 64bit. And it still seems to have a major bugs.
After certain days it will show a message: “Connectivity with the VPN service is lost”
The logs will contain something similar to:
21.06.12 09:48:00,752 com.apple.launchd: (com.checkpoint.epc.service) Exited with code: 1
21.06.12 09:48:00,752 com.apple.launchd: (com.checkpoint.epc.service) Throttling respawn: Will start in 10 seconds
21.06.12 09:48:11,981 com.apple.launchd: (com.checkpoint.epc.service) Exited with code: 1
21.06.12 09:48:11,981 com.apple.launchd: (com.checkpoint.epc.service) Throttling respawn: Will start in 9 seconds
21.06.12 09:48:21,465 com.apple.launchd: (com.checkpoint.epc.service) Exited with code: 1
21.06.12 09:48:21,465 com.apple.launchd: (com.checkpoint.epc.service) Throttling respawn: Will start in 10 seconds
CheckPoint Secure Client on Mac OS X 10.6.6 on a newer MacBook Pro (Mid 2010), (Early 2011) fails – solved
Posted on 18 March 2011 | 6 responses
As stated on Apple’s Support page in this Article newer Mac’s boot up in 64-bit kernel by default. If Checkpoint Secure Client is needed to be used, this will not work together. This is due to the fact that Checkpoints VPN Client is only 32-bit.
So in order to get it working, the Mac OS needs to run with 32-bit kernel as it did on the Macs earlier by default.
Please follow this article on Apple’s support page to switch back to 32-bit kernel and you will get Checkpoint’s VPN Client running.
Posted on 7 December 2010 | 38 responses
After upgrading to 10.6.5 and now also 10.6.6 many users had issues with DNS/network. This issue is causing timeouts in browser or at least long delays. See this thread.
But thankfully user KJK555 found a good workaround. It replaces concerned files of the new mDNSResponder with older 10.6.4 files.
Just install this package and reboot.
Posted on 8 September 2009 | No responses
NetApp (OnTap 188.8.131.52) is not able to join with authentication on an NT4 Domain or Samba PDC. In order to join the Filer to such a Domain the machine account needs to be created before. That works so far on a normal Samba PDC. But this does not work on a Mac OS X 10.5 or 10.6 Server.
I tried to add the machine to the OpenDirectory before. The Filer messages shows that the connection gets terminated during the join process. This was very frustrating as you can imagine. Losing your connection is very annoying, whether you’re going through a tunnel on a train with your O2 Dell Streak Mobile broadband or a network connection cannot be forged. This is a real bugbear of mine and I am determined to fix it.
Posted on 7 September 2009 | 14 responses
There seem to be an issue with Snow Leopard accessing a CIFS Share on a Filer. Especially copying of Files ends up with the following Error:
The Finder can’t complete the operation because some data in “<filename>” can’t be read or written.
(Error code -36)
The files on destination do exists afterwards. They also seem to be correct. Just the Error message shows up in general.
I also realized that this happens only on certain users. So I will investigate more about the differences.
Posted on 7 September 2009 | 45 responses
As in my previous post I describe a method to have SecureClient R56 running on Snow Leopard. However, if you have a lot of machines to be installed an VPN Client, it might be worth just doing the changes inside the package. So it must be done only once. All you need to later, just running the Package on Snow Leopard without editing anything.
It requires some knowledge using the shell, so a basic understanding of Linux commands would be good.
To get around the Leopard Check
- edit two Files inside the package (Right-Click on the Package / Show Package Contents. This opens finder within the package.
Posted on 7 September 2009 | 3 responses
Once you want to uninstall SecureClient R56 HFA1 on Snow Leopard, it might leave 2 or 3 files on your receipts folder. This is not a big issue as long you are not reinstalling the SecureClient. But if so, the installer will end with “succeeded”. Unfortunately SecureClient is not in the Application folder nor in /opt. Nothing really is installed.
After you uninstalled SecureClient with Checkpoints uninstaller (Application/Checkpoint/uninstall) you have to remove 2 or 3 files in a receipts folder. Afterwards a new installation of SecureClient should be really succeed in showing up the Application.
Posted on 3 September 2009 | 296 responses
We all remember, once Leopard was out it took Checkpoint quite a long time to update their VPN client. Now Snow Leopard is out and it begins …
After installing Snow Leopard, Checkpoints SecureClient refuses to install and if already installed (through an upgrade) it won’t start at all.
I did some investigation and I finaly made it working since Apple hasn’t changed too much.
1. The Checkpoint installer refuses to install
The installer checks up for the Darwin Kernel version 9. In Snow Leopard we have version 10. So two files need to be edit within the installer package.