So I have kind of a weird one. We were using IPSec for endpoint user VPN access and we recently switched to SSL VPN. We are using the Sophos Connect 2.1 client and created a brand new .pro file for the SSL VPN connection. We turned off IPSec remote access on the FW. Whether you delete the old config file in the sophos connect client or are a new user being set up.. once you connect to the SSL VPN, it somehow populates the sophos connect client with the old IPsec VPN configuration as well. I feel like this has something to do with how the sophos connect client uses the end user portal on the back end. I am not sure how to get it to stop automatically pulling down a config that is turned off.
Upon reboot of the PC, the sophos connect client has the IPSec connection (currently disabled on the FW) in the first position and the SSL VPN connection in the second position so users automatically connect to the incorrect connection.
It is causing a support headache and I am really confused at how these devices are "pulling down" a config as it is not my understanding of how this sophos connect client works....
Any assistance or insight on how to stop this would be really appreciated!
This thread was automatically locked due to age.