Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Suggested Answer
  • +3 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 43 subscribers
  • Views 2236 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Connect client looses profile when changing network

Stéphane Kamdem

We are experiencing a very strange effect with the Sophos Connect 2.2.90 client

We use SSL VPN connections for users.
Users load the profile from the user portal and import it into the client.
The connection works fine, but when the user switches networks (i.e., from their home office to where they downloaded the profile at the airport), the profile disappears.
This phenomenon has been observed in several users.
Each time the user changes networks, he must download and import his profile again.

I saw that an update of the Sophos Connect 2.3.0.0506 Client was available, and I implemented the update on my entire computer park via Intune. However, she could not settle.

Trying to do this manually and with an account with super admin privileges, I have the following error:
ovpn service does not have sufficient rights to start services.

Could you help me correct this incident.

Waiting to read you.



This thread was automatically locked due to age.
  • 0

    You can read about this more here :  Sophos Connect Client - disappearing SSL VPN connection  

     Sophos Connect client looses profile when changing network 

    Could be because the network changes or the user changes in Windows. It is already on the backlog to fix this in the future.  

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    Thanks for your confirmation that Sophos has still not fixed this after years and years, and dozens of reports in the Sophos Community, which have all been chocked off due to a stupid Sophos forum configuration that doesn't allow to continue a discussion in the original thread.

    Confirms my thoughts that it's not not worth looking at new Sophos products when our good old UTM will need replacement. If you cannot fix a problem that causes so many support calls, then your processes are not ready for prime time. Don't even suggest I open a Sophos support ticket. Last experience with your incompetent AI bots was enough.

    I have not heard about this problem with the original OpenVPN client, so I will have to waste more time trying and evaluating that software.

  • 0 in reply to Markus Keller

    Forget Sophos Connect. You can wait years before anything happens. Seems the dev-team for connect is non-existent (or some we-have-to-save-money outsourced company). Tons of bugs and nothing has happened since 2.29 (sorry, not true - even more bugs).

    They don't even manage to maintain the Known Issue list of connect.

Unfiltered HTML