05-26-2003 05:35 PM - edited 02-21-2020 12:34 PM
I have multiple people try doing a VPN client upgrade. I have seen it going from 3.1.1 to 3.6.4. I dont think it is the to/from version. The install removes the old client, reboots, and installs the new client, and reboot. At this point, I have no connectivity. Uninstalling or reverting to the original version does not resolve the issue.
I believe it to be with the DNE. What is the process to recover from this condition.
Thanks,
Dan Laden
05-30-2003 10:29 AM
I don't think that there are any known issued related to the process of upgrading the VPN client, similar to the one you described. The issue probably is not with the VPN client. If you have used the upgared procedure as described at http://www.cisco.com/en/US/products/sw/secursw/ps2308/products_user_guide_chapter09186a00800ecb3e.html#xtocid24, your existing connection entries should have been retained.
06-17-2003 01:57 PM
We are doing a rollout of iPass with the EZVPN clilent 3.62. On multiple 2000/XP machines the client will corrupt the DNE and trash a registry entry so you cannot delete the local_machine\software\deterministicNetwork\DNE\Parameter key.
on XP, the machine had no rollbacks over a week. I was able to install IP6 and cleared the corruption but this is a once only fix. It is deffinitely the DNE subsystem that appears to be a problem. It still did not fix the problem.
VPN Subsystem not available, ect. one tail tell sign. Specifically on XP, if you get NO unsigned driver warnings, your system is corrupt and so is that key in the registry.
Any answers ANYONE?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide