Well, I am having the same problem and have been trying to fix it now for the last two days trying everything I can think of from uninstalling the latest Vista updates (which is the only thing that changed as far as I know between the VPN working normally and receiving this error).
From the amount of information that is out there, it appears to be a big problem for many people and our good friends here at Cisco are not responding.
The latest version of the VPN client I believe is 5.0.3.0530 which I installed. Although I am sometimes (after cleaning the registry of all references to Cisco and then re-installing the product) able to start the client... but then I get the 442 error.
The latest version, according to the release notes, is supposed to have fixed the error but obviously Cisco is running after the facts and not being pro-active or creating a solution that is stable and won't be affected by Vista upgrades. In any case, nothing is working for me either and I can't connect to my client's network to do work that has deadlines... I am screwed and lost two days of work already because of this.
OK, I have come a little bit further with this problem. Some recent automatic updates by Windows Vista caused the client to stop working when it was working before.
I uninstalled all the updates (most were critical security patches which now leaves me vulnerable) and uninstalled the Cisco VPN client including scouring the Registry for anything remotely associated with the VPN such as any reference to 'CVPN' or 'Cisco'.
I then installed the latest VPN client (V 5.0.03.0560), and I DIDN'T reboot as it asked me too. The reason I thought this was a good idea is because after a reboot, the Network Connections are reset and re-assigned IPs which was, I started to think, part of the problem.
It Worked! I was able to start the client (that was already an achievement!) and, lo and behold, was able to connect without problems... I thought!
Now I have the following... when I connected to the VPN, I have limited access to the internet. Some sites are fine, others only load half-way and still others I can absolutely not connect to. The ones I can connect to load very very slow.
For now I have left it this way since I can (albeit handicapped) connect to the VPN so I have to keep connecting/disconnecting etc. It is still very frustrating.
However, I believe I know what the problem is, but I don't know how to solve it. If anyone here can use this information to take this one step further, we may get somewhere.
I believe it has to do with the TCP/IP settings where we now have both v4 and v6 running. I think the VPN is using one of these only, and when it is using it, it is not allowing any other traffic through it. I don't know how to solve this. I tried disabling one or the other in either Network Connection, but it either gives me no connection or limited connection.
The reason I think this is it is because some sites are loading/half loading when the VPN is connected... in other words, one of the TCP/IP protocals is open to the Internt traffic, the other is used by the VPN exclusively.
I tried looking for sharing and tunneling options in my VPN client and the Network Connections settings, but I can't find anything.
I am very hesitant to change any more settings since I do have a half-baked solution that at least allows me to meet the deadlines I have for my client.
Windows Vista + VpnClient = reason 442, locally adapter terminated
I tried everything, from upgrading vpnclient, reboot, interface diagnostic, add some keys to the registry, and other magicals receipts. But the only thing that work was disable the ICS service, and starts it manually when I needed it.
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...