Anyconnect with SBL not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2010 02:50 PM - edited 02-21-2020 04:51 PM
I am trying to get the SBL to work for Windows XP/Vista/7 using an ASA5510 running 8.2 (1). When I login to the WebVPN, it installs the anyconnect client and SBL components, and copies the xml profile. When I reboot, I get nothing popping up (on an XP machine) before login...any ideas? I have included below my config for the webvpn...I also worked with TAC and they could not find the problem either. Any help you can give me is appreciated.
webvpn
enable outside
svc image disk0:/anyconnect-win-2.5.0217-k9.pkg 1
svc profiles profile1 disk0:/AnyConnect.xml
svc enable
group-policy WebVPNPolicy internal
group-policy WebVPNPolicy attributes
wins-server value 192.168.2.10 192.168.2.13
dns-server value 192.168.2.10 192.168.2.13
vpn-tunnel-protocol IPSec l2tp-ipsec svc webvpn
split-tunnel-policy tunnelspecified
split-tunnel-network-list value WebVPNACL
webvpn
svc modules value vpngina
svc profiles value profile1
- Labels:
-
AnyConnect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2010 11:37 PM
Hi,
Could you please confirm:
- If you have enabled SBL in the profile (per http://www.cisco.com/en/US/docs/security/vpn_client/anyconnect/anyconnect20/administrative/guide/admin7.html#wp999891)
- That the correct profile has been passed down to the client (this can be found under "C:\Documents and Settings\All Users\Application Data\Cisco\Cisco AnyConnect VPN Client\Profile")
- If you still see this issue after renaming the xml profile to something else and having it pushed down again (to ensure we are not using a cached version of the profile.
Thanks,
Steve.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2010 08:21 AM
Thanks for the reply! I actually did not change anything and it is working this morning. This leads me to believe it was a PC issue. Thanks for the reply!
