VPN (vista) ipconflict

Right from the support site of Cisco: Here is the process the client goes through:

1. Authenticates with the vpn appliance.
2. Receives parameters from the appliance which includes private IP address, etc.
3. Client then assigns the IP information to the Virtual Adapter.
4. Client then enables the virtual adapter.
5. Client checks to ensure the virtual adapter is enabled and then changes status to connected.

What is going on:
When the client assigns the IP information and enables the adapter, Vista is causes a false positive IP address conflict, for whatever reason and shuts down the virtual adapter. This will cause the client to hang at "securing connection".

What you might also have happen is that when the client assigns the IP address to the virtual adapter and enable's the adapter, the client checks to see if the adapter is really enabled, this is done by enumerating the adapters looking for the assigned IP. Vista now stores the IP information for the adapters is a hidden store and we do not have API control over this and can't ensure that there is no old IP address in there, sometimes Vista hangs onto the old IP even though we tell it to clear it after disconnect, when we enumerate the adapters vista returns the old IP not the new IP and the client things the adapter is not enabled, again causes the client to hang at securing connection.

Unfortunately there isn't much you can do on your machine to resolve this. See my post above for some workarounds but ultimately there isn't something enduser can fix, it's something that we need fixed by MS, in the meantime we are adding more "hacks" to our code to work around the MS lack of API access to the network stack.

Richard