01-18-2018 08:25 AM - edited 03-12-2019 04:55 AM
Hello,
I use Cisco AnyConnect to connect with a few outside networks.
Normally the Cisco client looks like this:
And I can type in any gateway and connect right away.
Recently I got a new customer connection that is stored in the form of an XML file in the
"C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Profile" folder.
And because of this one profile being there the window in the cisco client, where I normally type in the gateways, becomes greyed out.
Is it possible to override this (maybe some file editing, or registry editing) so that I can have both?
- the profile on the dropdown list from the "Profile" folder
- the ability to type in gateways manually at will for her connections
Best regards.
Solved! Go to Solution.
01-18-2018 09:00 AM
I am guessing the xml you have just downloaded has allow manual host input disabled.
The simplest thing you can do is delete the xml and restart the anyconnect, but next time you connect to the same ASA the xml will be downloaded again.
You could also modify the xml in any text editor.
Cisco also provides a tool called VPN Profile editor for offline editing, or if you have access to the ASA you could use ASDM.
HTH
Bogdan
01-18-2018 09:34 AM - edited 01-18-2018 09:35 AM
That did the trick!
I edited the profile XML file and changed
<AllowManualHostInput>false</AllowManualHostInput>
to
<AllowManualHostInput>true</AllowManualHostInput>
Works like a charm.
Thank you very much Bogdan!
01-18-2018 09:00 AM
I am guessing the xml you have just downloaded has allow manual host input disabled.
The simplest thing you can do is delete the xml and restart the anyconnect, but next time you connect to the same ASA the xml will be downloaded again.
You could also modify the xml in any text editor.
Cisco also provides a tool called VPN Profile editor for offline editing, or if you have access to the ASA you could use ASDM.
HTH
Bogdan
01-18-2018 09:34 AM - edited 01-18-2018 09:35 AM
That did the trick!
I edited the profile XML file and changed
<AllowManualHostInput>false</AllowManualHostInput>
to
<AllowManualHostInput>true</AllowManualHostInput>
Works like a charm.
Thank you very much Bogdan!
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