Windows Server 2003 mistakenly complains about the Zone Labs vsdata file included in our product and warns users to upgrade to a newer Zone Labs product rev, even though the full Zone Labs product is not installed.
We have addressed this in the 4.0.3 release of the VPN Client by including a new vsdata component from Zone Labs, so the 4.0(3) client should work for you. The 3.x version of the client will never be made compatible with 2003, so you'll need to upgrade.
jins - were you able to get the V4.0.3 VPN Client to work with your Windows 2003 Server OS? I've been trying the same thing, and have run into a problem with the VPN Client not able to add routes to the PC's routing table when the VPN tunnel comes up. I was interested to see if yours is working. Thanks.
jins - on the Cisco VPN Client turn the logging settings all to high, open the log window, and start the VPN Client. This is where I noticed that the VPN Client was not able to add routes correctly. It gave an error indicating that is was unable to add routes.
As a workaround, I put together a little batch job that takes the routes from my VPN concentrator that I normally give the PC when the tunnel comes up, and run that on the PC manually once the tunnel is up. This seems to resolve the problem. The problem with this is the virtual adapter's IP address changes, so you need to be able to change that in the batch job to reflect the changing IP address of the virtual adapter in the route table, since it changes from connect to connect.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...