THe problem Ronnie is talking about deals with Cisco VPN's ability to
"Startup". The Subsystem (Cisco VPN Client Service) must start before
you log into the computer. If you do not wait, you will receive the
error, and not be able to vpn, unless you manually start the client
service, then run the client software.
Cisco recommends you wait a moment, before logging into the PC so it
has a chance to startup.
We experienced this problem with some users of 3.6.2 and specially
when we wanted to VPN prior to login.
Have patience!
"Ronnie C" <(E-Mail Removed)> wrote in message news:<062701c39849$8bce6620$(E-Mail Removed)>...
> I'm having a problem with the Cisco VPN adapter client
> application and Windows XP.
>
> It works for the first time I install it and connect up to
> the corp network using the VPN service over ADSL......
> When i finish working on the corporate network, I
> disconnect the link and naturally switch off the laptop.
>
> When I next try to use it, it won't open the application
> without first giving the error screen that the VPN sub-
> system is not available and it then is not able to open
> the connection at all no matter what. I manually disable
> and reenable the cisco vpn adapter however I always am
> stucks with a 0.0.0.0 ip address on it (using dhcp) and
> can't ever release it to renew with the corporate network.
>
> All I can do to make it work at this point is to uninstall
> the applcation, reboot the laptop, reinstall it, reboot
> again, and then it works again for the next connection....
>
> One I disconnect the VPN connection again though, the
> error appears again and I am forced to go through the same
> reinstallation process.
>
> Do you know about this problem or is a service pack/later
> version of vpn
> client available? I have this problem in both Cisco
> Version 4.0.1(rel) and version 4.0.2 (d)
>
> I am running win Zp with SP1 and most of the windows
> update patches. As I was uninstalling the application, I
> occasionally get a blue screen in relation to the tcp
> adapter and the crash report that I send to microsoft
> identifies that the ultranav drive (ibm t30 laptop) is the
> cause. I've updated this driver with the latest version
> also.
>
> Very weird problem though as others in office are running
> the same set up as I am and I am the only one experiencing
> the problem
|