Cisco Secure Client Auto-Upgrade Causes First VPN Connection Attempt to Fail
1 vote
Hello,
we noticed a usability issue when using the Cisco VPN extension in Remote Desktop Manager.
When a user starts a VPN connection through RDM and the VPN gateway initiates a Cisco Secure Client upgrade, the Cisco client restarts during the connection process. As a result, the first connection attempt fails.
After the upgrade has completed, the user simply has to start the VPN connection again and everything works as expected.
Would it be possible to add an automatic retry mechanism for this scenario?
For example, if the VPN process terminates during connection establishment, RDM could wait a few seconds and automatically perform a second connection attempt. This would make the update process much more seamless and would avoid confusion for users who currently see the first attempt fail without realizing that the VPN client was upgraded in the background.
We have reproduced this behaviour multiple times and Devolutions Support confirmed it and suggested creating a feature request.
Thanks for considering it.
CiscoSecureClientUpdateFailStepByStep.pdf
Hello,
Thank you for the request. We'll have to analyse how the program currently works to see how feasible this is. Some VPN executables don't stay opened after establishing connection, as it might be a service or a different executable that will maintain the VPN connection, meaning the executable will always close and we may not be able to detect whether it was from a successful connection or from a failed one (thus needing us to retry).
I've opened a ticket for this.
Regards,
Hubert Mireault