Filter
Top Products
Caveats Resolved in Release 4.0.4.B
66
Release Notes for VPN Client, Release 4.0 through Release 4.0.5.D
OL-5450-10
• CSCee30728
When the VPN Client Release 4.0.3.F is installed, uninstalled, and
reinstalled, the VPN Client cannot establish a tunnel. The client logs have the
message:
Failed to initialize the ipsec driver! Returned 1
• CSCee50403
The Linux VPN Client 4.0.4.A will not install on the SuSe 9.1 OS.
• CSCee50587
Certificate import screens introduced in the 4.0 VPN Client that say that a
password is optional may be confusing to some users. Customer would like
the message changed to say that a password may be required instead of that a
password is optional.
• CSCee54475
Firewall dialog box needs to be disabled if firewall is not used.
At SBL (Start Before Login), the VPN Client checks to see if any supported
firewalls (Zone, BlackIce, etc.) are installed on the system. If they are, the
client checks to see if they are up and running. If they are not up and running,
the client displays a dialog box letting the user know that we are waiting for
the firewall to start before continuing with the VPN connection. Users have
an option for canceling this dialog box and continuing even though the
firewall has not started. This happens before the client has sent any messages
to the VPN 3000 Concentrator; therefore, the client has no idea if a firewall
is in fact required by the VPN 3000 Concentrator. We wait because we don't
want to start a connection to the VPN 3000 Concentrator until an installed
firewall is up and running, for security reasons.
This needs to be done because sometimes at SBL, the Cisco VPN Service
would come up before other services (like the firewall), or the TCP stack.
This is seen more often on Windows XP, because XP has the fast boot option
where a user is allowed to log on the system even before all the services are
up. If a firewall is required by the VPN 3000 Concentrator device, we want to
make sure that the firewall is up.