- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2015 07:35 AM - edited 03-11-2019 11:09 PM
Over the last week, I've seen several clients (mostly windows 7 and Vista, not seen yet on Windows 8.x) having the same problem.
When connecting to our VPN services on ASA 5510 running version asa915-k8.bin
Clients are connecting with AnyConnect version 3.1.06079
The AnyConnect client opens normally. The user enters the name of our server for connection.
The user sees "Waiting for user input" in the client main window. This is normal and advises that the log in prompt box will appear.
The log in box never appears.
One user did a Windows Recovery revert to previous date and all worked again. This is obviously a case of a Microsoft update causing new problems for the AnyConnect client but I'm unsure what update. Should I find an upgrade tor the VPN client? Has Cisco patched for this?
I'm hoping for a suggestion. Any help will be useful.
Thanks,
John D.
Solved! Go to Solution.
- Labels:
-
NGFW Firewalls
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2015 07:27 PM
I experienced this same issue on a Windows Vista client as well. Removing KB3057839 solved my problem. I hope this helps out.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2015 09:08 AM
moving this post to the appropriate Firewalling Community for expedient responses.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2015 02:01 AM
We had this issue also with some Windows Vista Client.
The workaround was also to deinstall the latest Windows patches.
But unfortunately we don't know whitch update had caused the issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2015 07:27 PM
I experienced this same issue on a Windows Vista client as well. Removing KB3057839 solved my problem. I hope this helps out.
