|
Do not be so sure CP is the culprit here. I
have seen problems before with the Novell client and other vendors VPN clients
including Cisco and Enterasys, particularly when doing IPSec. It seems
that the Novell client messes with the IP stack somehow (I was never able to get
a straight answer) and in some versions of windows this can cause negotiation
failures with the VPN servers. Try checking the Novell web page and see if
they have any hints for you. Unfortunately, they did not for
me....
In our scenario, the order of installation
determined the upgrade path. If the VPN client was installed first and
then the Novell client, a second installation (after the Novell client) of the
VPN client worked. If the Novell client was installed first, we did not
have reliable installations without re-installing the OS. For some, with a
clean OS install we did not see the problem at all.
----- Original Message -----
Sent: Thursday, April 25, 2002 2:02
PM
Subject: [FW-1] Login process priority
after installing SR client (Novell)
Can anyone tell me why when I
install the SecuRemote client on my machine my Novell Client login get
hosed.
The system only prompts using
the Windows window. The only way I can get it back it to reinstall
Novell.
It all seems to work OK
afterwards but it's going to be a real problem if I have to upgrade a couple
of hundred laptops.
Paul
PS: moan.. moan... Why can't Check Point
release a working version of SR client I am also getting fed up with the 'Not
signed' boxes I keep having to clear on XP.
| 
