I have been noticing that any time I try to use the Cisco AnyConnect VPN I have to start it manually as the remote desktop manager cannot open it. It will close it when I close a RDP session it just wont open it or start the connection. I am currently running Cisco AnyConnect Secure Mobility Client version 3.1.05160 and the startup is located in "C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpnui.exe". So the question would be that since it can close the client when I disconnect why can't it open it when I try to connect?
Hi,
Could you verify if you have an error message in the application logs located in Help->View Application Logs. Does it also happen when you execute RDM with the Run As Administrator?
David Hervieux
I cleared the log and then tried to connect to a machine that requires the VPN to be connected and after letting it go through the entire cycle I checked the log and it is still had no issues showing. Below is what is showing when I bring the log file up in notepad with the connection name removed.
[5/13/2014 9:07:13 AM] VPN connected ************* ()
[5/13/2014 9:08:18 AM] Connecting to '***************' (Microsoft Remote Desktop (RDP))
[5/13/2014 9:08:40 AM] Disconnected from '*****************' (Microsoft Remote Desktop (RDP))
[5/13/2014 9:08:41 AM] VPN disconnected (Wayne Community College)
I then tried to do it with Run As Administrator and received the same results. I can see where the command box opens but it doesn't stay open for very long before going away so can't take a screen shot of it. I have also tried to go through and edit connections and test the connection from the VPN tab and I get the same results. It's like it never calls up the VPN client.
Just for a test, could you try to open it in a command line box:
C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\vpnui.exe connect {hostname}
David Hervieux
You and I are thinking along the same lines as I was just in the process of trying that. I did get it to bring the client up through the command line but it doesn't start the connection at all. I tried vpnui.exe connect 192.86.xx.x as well as vpnu.exe connect \192.86.xx.x and the only thing that happens is the client is brought up on my screen.
This is strange. Do you think it could be related to your AnyConnect version?
David Hervieux
David,
I think I may have it on an AwHa moment. What I have found is the RDM is calling up the vpnui.exe when it should be calling up the vpncli.exe in the command prompt window. Or at least that is what I am getting from other google searches that I did. If you go to a command prompt window and go to the correct folder and type in vpnui.exe you get the client to popup on your screen, but if you type in vpncli.exe connect (client) it will ask you for the user/pwd. Hope that make sense.
I think you might be right. We have this todo on our list:
http://forum.devolutions.net/messages.aspx?TopicID=1869&MessageID=53041#post53041
David Hervieux