Cisco Bug: CSCun19159 - Hostscan should use the IP address of the first ASA it connected to
Mar 15, 2016
- Cisco AnyConnect Secure Mobility Client
Known Affected Releases
Symptom: HostScan sends traffic to an ASA other than the one that AnyConnect initially connected to. Conditions: This issue can occur if you resolve your ASA IP address to two different IP address externally and internally. The initial VPN connection will be established via the external IP address. Once VPN is connected it is possible that Hostscan will perform a DNS query and resolve the ASA IP address to the internal address of a different ASA. This will cause Hostscan to fail.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases