Anyconnect 4.2.00096 Address Issue

[Justin Schwilling]

I have a client that uses the Cisco Anyconnect Secure Mobility Client version 4.2.00096.  With previous builds of the AnyConnect client, you could launch the Windows client, and in the address bar it woudl list the address of the last VPN you connected to (ex: vpn.contoso.com). With this current version, it seems the address history is not retained.  I can see why this would be a security feature for some, but there are some clients who may not remeber a DNS name for the vpn tunnel they want to connect to, and I know users woudl struggle if they had to remeber an ip address for their VPN tunnel. 

Has anyone else noticed this or found a fix to get it to display the address of the last VPN tunnel you connected to?

[rvarelac · Accepted solution]

Hi Justin, 

That customization part is configured under the XML profile, specifically on the server list tab. Check the link below for a configuation example:

https://supportforums.cisco.com/document/12550601/anyconnect-xml-settings

You also might want to check the xml profile installed on the computer it is located on the following folder:

%ProgramData%\Cisco\Cisco AnyConnect Secure Mobility Client\Profile

Hope it helps

-Randy-

[swj]

Hi Justin, 

Just wanted to ask after the change was it working ?

If so could you please tell me what changes you made. As of I am aware there was a problem with 

4.2.00096 Anyconnect version in reading the existing XML profile. 

I found an external bug. Thinkig you are hitting this bug. 

https://tools.cisco.com/bugsearch/bug/CSCux13036/?reffering_site=dumpcr

So just want to conform. Let me know the update. 

Thanks 

swj 

[Justin Schwilling]

Creating a profile and adding the client's VPN address in the server list seems to have helped.  Although before we did nto sue profiles, we just installed the client and the last visited VPN address woud be remebered.

This is a workable solution though.

[swj]

Hi Justin, 

Yes that is clear to me now. I was thinking you have the profile previously and it was not detecting now in the newer version so provided you the bug which  failed in the new version any connect 4.2.00096.  

Its glad your issue got resolved.

Wish you a great day. 

Thanks

swj