I ran into a problem recently while I was using remote desktop on one of my servers hosted up on Azure. While I was on that server, I needed to make a VPN connection back to our corporate network. Unfortunately, after I installed the Cisco AnyConnect client, and I tried to make the connection, I was greeted with the following error:
- Still, VPN connections traverse external networks, and the encrypted VPN does not enhance the availability of remote connections. Also, VPNs with encrypted tunnels can affect the organizational capability to adequately monitor network communications traffic for malicious code.
- 'VPN establishment capability from a remote desktop is disabled. A VPN connection wil not be established' I have looked in the ELS-IMelAde-TCP.XML connection profile and the settings seem to allow it according to the Cisco VPN XML Reference ( Table A-19 ) SingleLocalLogon.
- I am using Anyconnect (ver. VPN is working from desktop, but doesn't work through RDP connection. In the XML file the following settings about remote session was changed to: SingleLocalLogon AllowRemoteUsers but anyconnect doesn't work.
- VPN Establishment capability from a Remote Desktop is disabled To get this to work you'll probably want the latest Any Connect client, and you'll need to modify the Any Connect Profile.tmpl file. The file can be found on your machine (once the client is installed).
VPN Establishment capability from a Remote Desktop is disabled To get this to work you'll probably want the latest Any Connect client, and you'll need to modify the Any Connect Profile.tmpl file. The file can be found on your machine (once the client is installed).
VPN Establishment capability from a Remote Desktop is disabled. A VPN Connection will not be established.
I did a lot of research, and found out that in order to allow this, you need to first setup a Client Profile on the Cisco ASA. Here are the steps I went thru to get this completed.
Vpn Establishment Capability From A Remote Desktop Is Disabled
- Launch the Cisco ASDM
- Click on Configuration.
- Expand “Network (Client) Access”
- Click on “AnyConnect Client Profile”
- Since, I did not have any existing profiles, I clicked the Add button.
- Pick a name for the Profile.
- Select the Group Policy that this profile will apply to, and click OK
- Before editing the profile, click on the Apply button to generate the XML file.
- Under “Preferences (Part 1)” go to “Windows VPN Establishment” and select AllowRemoteUsers from the drop down, and then click OK.
- Click on the Apply button to update the XML file.
- You should now be able to test connecting to your network from within a Remote Desktop session.
- Assuming everything works as expected, I recommend hitting the Save button to write your configuration to memory.