HP Sa3110 - VPN Server Appliance Release Notes page 34

VPN Client on NT4 System Does Not Bind
To 3COM 3C515 NIC
Reference Numbers 554P and 721
In Release 6.8.2, the VPN Client on an NT4 Workstation
and Server with SP6 will not bind to a 3COM 3C515 NIC.
When you try to establish a tunnel, this NIC is not listed in
the Tunnel Properties window in either IPSec or SST.
Static IP Interface Route Is Removed
After Tunnel Disconnect
Reference Number 618
If a machine is multihomed and has static routes, you may
see the routes disappear after the VPN tunnel is
disconnected. When the static IP interface route statement
is removed on a multihomed interface. This results in the
host not being able to contact local nodes in the subnet.
Device Name Not Displayed If Used In
Place of IP Address
Reference Number 768
If you connect the VPN Client using the device name in
place of the IP address, the device's address is displayed as
the Peer IP instead of the device name. This happens only
when using IPSec, not when using SST.
Transport Mode IPSec Tunnel Connection
Eliminates Non- Tunnel Packets
Reference Number 706DF
When a Transport mode IPSec tunnel is up between a VPN
Client on Windows NT (SP4) and an HP VPN device
running Release 6.8.2 code, and the packets are targeted
towards either of the device's interfaces, non- negotiated
packets disappear. When the Transport mode tunnel is
down, packets such as ICMP pings and VPN Manager UDP
traffic go through to the device in the clear.
34
Hewlett-Packard SA3000 Series VPN Client