Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

A fix for Checkpoint SecureClient under 10.3.9 Network
This was developed by a colleague of mine and works (it was tested on a G3 Blue/White, and a G4 PowerBook).
  1. Create a text file called wdog.sh containing the following:
    #!/bin/tcsh 
      cd /opt/CPsrsc-50/bin 
      while (1) 
        ./SR_Service 
      end
    
  2. Put the file in /opt/CPsrsc-50/bin (use sudo).
  3. Type sudo chmod 755 /opt/CPsrsc-50/bin/wdog.sh to make it executable.
  4. Type sudo chown 0:0 /opt/CPsrsc-50/bin/wdog.sh to change the owner.
  5. Edit /System: Library: StartupItems: SecureClient: SecureClient (again, use sudo).
  6. Comment out this line:
    $SRDIR/bin/SR_Watchdog &> $SRDIR/log/ScBootlog.txt &
    by adding a # before it.
  7. After that line, add this new line:
    $SRDIR/bin/wdog.sh &> $SRDIR/log/ScBootlog.txt & 
Reboot and enjoy!

[robg adds: 10.3.9 broke the Checkpoint VPN; this is apparently a fix, though I don't use Checkpoint, so I can't test it.]
    •    
  • Currently 2.67 / 5
  You rated: 5 / 5 (3 votes cast)
 
[11,243 views]  

A fix for Checkpoint SecureClient under 10.3.9 | 9 comments | Create New Account
Click here to return to the 'A fix for Checkpoint SecureClient under 10.3.9' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A fix for Checkpoint SecureClient under 10.3.9
Authored by: hintbw on Apr 21, '05 12:43:04PM
Okay, I created the wdog.sh file and tried to edit the file you mentioned, however I ran into the following problems: I couldn't see where the alias linked unless I was root. When I could the file you referred to was a unix executable and I'm not sure how to "edit" it. I tried pico but that didn't work. Any ideas for us common people. I'm on a G4 Powerbook at 10.3.9 (obviously).

[ Reply to This | # ]
A fix for Checkpoint SecureClient under 10.3.9
Authored by: hintbw on Apr 21, '05 05:35:51PM

Okay, I figured it out. I need to go down one more level and I could edit the SecureClient as was mentioned. It was easier to open terminal, change to root (using sudo bash) and then


cd /opt/CPsrsc-50/boot/SecureClient
pico SecureClient

Make the changes to that file as indicated above and save the file and reboot. You'll be all set - this hint worked for me.



[ Reply to This | # ]
A fix for Checkpoint SecureClient under 10.3.9
Authored by: msteck on Apr 21, '05 05:57:27PM
You are right ! That way it does not work, the path to the file to edit is not written correctly (no colons), it is of course :
  /System/Library/StartupItems/SecureClient/SecureClient
so in your case it would be :
  sudo pico  /System/Library/StartupItems/SecureClient/SecureClient
Near the beginning you see "SecureClient SystemStarter Script", that is the one. Sorry about this, I guess I was so excited that I did not check it well enough.

---
Markus Steck
Bern (Switzerland)

[ Reply to This | # ]

A fix for Checkpoint SecureClient under 10.3.9
Authored by: raven42rac on Apr 21, '05 10:55:25PM

Step 5 should be
sudo bash
cd /opt/CPsrsc-50/boot/SecureClient
vi or pico SecureClient



[ Reply to This | # ]
A fix for Checkpoint SecureClient under 10.3.9
Authored by: endaff on Feb 02, '06 07:57:13AM

has anybody got a fix for this to work on tiger 10.4.4



[ Reply to This | # ]
A fix for Checkpoint SecureClient under 10.3.9
Authored by: franksting on Feb 12, '06 05:44:58PM

I don't believe that Checkpoint ever released a version that worked on 10.4. I can't update my mac at home to 10.4 for this reason :(



[ Reply to This | # ]
A fix for Checkpoint SecureClient under 10.3.9
Authored by: zerografix on Mar 02, '06 05:56:11AM

Me either - They should have had this done by now!



[ Reply to This | # ]
you dont need to reboot...
Authored by: drlabrat on Apr 22, '05 06:16:48AM

You just need to su to root or sudo the following:

/opt/CPsrsc-50/bin/scc start

(you can also use scc status to see if it is all up and running...)



[ Reply to This | # ]
A fix for Checkpoint SecureClient under 10.3.9
Authored by: bugmenot on Jul 11, '07 07:56:22AM

Checkpoint has an updated client that fixes this issue. Though at the moment you have to request it specifically.



[ Reply to This | # ]