ISEKI CISCO SYSTEMS OL-5450-10 - Manual (Page 71)

71
Release Notes for VPN Client, Release 4.0 through Release 4.0.5.D
OL-5450-10
Caveats Resolved in Release 4.0.3.C
• CSCea65393
Using the 4.0 VPN Client with the virtual adapter (Windows 2000 or
Windows XP) in a multiple NIC environment, the VPN Client might not pass
data while connected.
When the VPN Client PC has multiple network interfaces and the default
gateway is on the non-VPN interface, the default gateway metric is not
incremented. This might result in data that is bound for the VPN going to the
non-VPN default gateway and being dropped. This problem is clearly
identifiable by looking at the routing table while a VPN (All Tunneling)
connection is active, where the two default routes appear with equal metrics.
• CSCeb77199
The 4.0 VPN Client requires a specific route to the DHCP server so that this
doesn't break after the connection is established. If users are connecting to the
external interface and using a local DHCP server there is a specific route to
that server created pointing to the NIC, not the virtual adapter.
If other services are running on that same server, such as WINS, DNS, and
such, this route breaks these services once the VPN session is established. If
you remove this route, everything works as it should. This occurs regardless
of whether you use tunnel everything or split tunneling.
• CSCeb77706
VPN Client, Release 4.0.2.B causes system failure (blue screen) when using
IPSec/TCP.
• CSCec61723
Cisco VPN traffic seems to top off at 1352 (IP datagram), which includes
1324 (ESP packet). This happens even when the interface MTU is set to 1400
or more.
• CSCec62565
In a load-balanced configuration running VPN Client Releases 4.0.1, 4.0.1.A,
4.0.2.C - E, 4.0.3, and VPN Concentrator Releases 4.0, 4.0.1.A - E, the DPD
fails to disconnect the Client IPSec session when the Client connects to the
load-balanced cluster IP address.