Filter
Top Products
75
Release Notes for VPN Client, Release 4.0 through Release 4.0.5.D
OL-5450-10
Caveats Resolved in Release 4.0.2.D
To activate “Start before Logon”, oem.ini and vpnclient.ini are present in the
installation package. Once the machine is rebooted after the installation, the
“Start before Logon” feature does not work.
• CSCeb12483
When making changes to the vpnclient.ini and preceding [CertEnrollment]
parameters with an exclamation point (!) character, the fields are still editable
after installation. The exclamation point should make these fields uneditable,
but users can still edit the fields after installation and rebooting.
• CSCeb27643
Information like Department information does not get filled in using v4.0.1
of the VPN Client. When using Certificate Enrollment, the CA url info is
correctly saved, but other information is ignored.
• CSCeb66861
On an XP PC with the 4.0 or 4.0.1 VPN Client, a user may experience DNS
issues upon connection. After connecting to a VPN 3000 Concentrator
(Release 4.0), the VPN Client can ping resources on the private network by
IP, but not by name. Once this happens on the XP PC, you can go to
network connections->advanced->advanced settings and change the order of
the adapters, or actually move a different (doesn't matter which) one to the
top of the list and hit OK. You can then ping by name.
If you disconnect the VPN Client and reconnect, you get the same results, but
the adapter at the top of the list is the one you moved there previously. You
cannot ping by name until you move a different adapter to the top of the list
and hit OK.
• CSCeb70819
The VPN Client intermittently takes as much as 30 seconds to launch. This
happens only intermittently. It takes about 15 seconds for the splash screen to
come up, and another 15 seconds for the GUI to come up. If you launch the
GUI from the command line or Windows Explorer by executing vpngui.exe
directly, it takes half that time.
This problem exists only in Releases 4.0.2, 4.0.2.A and 4.0.2.B of the VPN
Client. If VPN Client logs are disabled, this problem completely goes away.