10-09-2009 09:21 AM - edited 03-09-2019 10:37 PM
I am trying to set up the AnyConnect client (v2.4.0196) and when it tries to connect it fails with a no assigned address error. I look in the logs of the ASA and see a No IPv6 address available for SVC connection. IPv6 is disabled on the ASA.
Does anyone know how to prevent the AnyConnect client from trying to get an IPv6 address?
Thanks in advance...
10-12-2009 11:14 PM
Note that 2.4 is still beta, 2.3.2016 is the latest supported release today.
Having said that, I rather suspect an ASA issue than a client issue. Can you confirm whether or not an ipv4 address is assigned?
I.e. is there something in the logs like:
Oct 13 2009 09:05:55: %ASA-6-737026: IPAA: Client assigned 192.168.0.1 from local pool
Oct 13 2009 09:05:55: %ASA-6-737006: IPAA: Local pool request succeeded for tunnel-group 'DefaultWEBVPNGroup'
(note these are level 6 messages)
10-16-2009 01:25 PM
I downgraded my client to 2.3.0254 and still got the same result. What fixed it for me was adding the address pool to the tunnel-group DefaultWEBVPNGroup. When using the VPN wizard, the wizard asks you to create a tunnel group and assigns the address pool to this new group, but not to the DefaultWEBVPNGroup. I guess it must be a bug because the wizard makes no mention of this group, but in order to make it work, you have to use this group.
11-19-2012 09:28 AM
Worked for me. Thank you!!!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide