Cisco Anyconnect Secure Mobility Client version 3.1.05160 tried to update to release 3.1.06073 and users get "VPN service not available" and/or Failed to download AnyConnect Secure Moblity Client 3.1.06073. A VPN connection cannot be established. We remove and reinstall client and it occurs again. The way we are removing is add/remove and remove the three components (the reporting tool, secure mobility client and start before login moduel), then we if we only delete afterwards c:\Program Files (x86)\Cisco sub-folders the issue would return so after removal we started to do the following removal steps.
Delete the following sub-folders: C:\Users\”users NOVELL ID”\AppData\Local\Cisco\Cisco AnyConnect Secure Mobility Client C:\Users\”user’s NOVELL ID”\AppData\Local\Cisco\Cisco HostScan
Remove all files except for the one file; AnyConnectLocalPolicy.xml from: C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client
1/5/15 - same users (about 3) same vpn service not available issue again:
we have cisco anyconnect secure mobility cient 3.1.06073 and a few users with windows 7 sp1 have repeat vpn service not started issues when trying to connect to the client. We reinstalling removing the left behind cisco folders before reinstalling and it occurs again. We see symantec reporting blocks on vpnagent.exe, cscan.exe, vpnui.exe which shows up on affected and non-affected machines but this is all we had to try to resolve. Windows firewall looked good. if it was a firewall issue (Symantec or windows firewall) we would have more users affected, but we don't what is breaking the client we wonder?
We rolled back as well since reinstall was temporary fix. We are 3.1.05160 again since 3.1.06073 has a proxy pac bug which appears as root cause to vpn service not available with 3.1.06073. There were 2 other versions Cisco stated had similar bug.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...