VPN Troubleshooting : Window Closes
Hi ..
Is there some 'feature' I a missing when setting up a VPN connection in RDM.
I am trying to use the Cisco AnyConnect plug-in, and each time I try a connection the window closes before I can read what went wrong.
Is there some option I can 'check' to keep that window from closing ?
I just need it kept open for long enough that I can see where it's not inserting the connect whatever.
Thanks
All Comments (6)
Hello,
We'll work on adding an option for that. Could you tell me if it has time to type anything in the window like username, password, group, etc, or if it opens then instantly closes?
Regards,
Hubert Mireault
Well .. It's done a quick open-close at first, and I removed the https: from the connect string; which seemed to be one bug.
Now .. It opens .. connects .. and then quickly snaps off.
I think it may be the group selection or something ..
I did realize that it's another one that doesn't like a 1Password credential ... I had to manually add it in, rather than a credential entry.
As you seem to be manipulating a cmd window with the clipboard buffer .. maybe throw a pause into the structure, if the user toggles a 'debug' checkbox ?
Could you try creating a command line session in RDM, then in the command put:
<PathToAnyConnectExecutable> connect <Host>
Here's an example: C:\Cisco\vpncli.exe connect 192.168.1.1
Can you see if that works?
What is exiting is the cisco executable itself so it's a little difficult to debug on our end since we can't test this out. It could be helpful if you made a video and sent it to me at hmireault (at) devolutions.net.
Regards,
Hubert Mireault
Well, I'm less asking you guys to debug why it won't connect; as that's my problem.
I am more asking you guys to make a way for that cmd session window not to auto-close.
Normally, I don't mind it closing, as it helps getting it out of the way.
But there are times you want to be able to debug why something is not working, and then it would be great to have that window remain open; even if it's just a keystroke request / pause.
The AnyConnect command-line doesn't give us anything to keep it open if it doesn't work. In RDM in the command line session there is an option in Execution Mode tab which is "Keep command-line opened", could you try opening it with that in a command-line session? I want to see if this successfully keeps it open. If it doesn't, I don't think there is much we can do, unfortunately.
Regards,
Hubert Mireault
For any one else looking at this you need to ensure that the Cisco client is not running when Remote Desktop Manager tries to open Cisco VPN since only one can be open at a time.