I had actually downloaded it successfully before, but for some reason after connecting to my school’s secured wifi (where you have to login and stuff) this error showed up.
I tried forgetting that network and trying it on a different network and everything, but this keeps showing up.
I’m downloading Cisco Secure Client version 5.1.3.62 and I’m on MacOS Sequoia beta.
Welcome to OSX Beta. Not trying to be a A$$ here but expecting everything to work on a beta build OS when the vendor more than likely is just starting to test with it is unrealistic. This is the first Beta build of the OS and very early in development. Cisco will more than likely will not ship a documented compatible version until after the OS is officially released. Hate to say it but your only option might be to downgrade OSX if this is your only device and need connectivity.
You could try the latest the latest 5.1.4.74 release, but Cisco generally doesn’t offer support until close to, or slightly after, public release. Even within a major OS release, Cisco has had to update the client for point releases. You may find better luck installing Sonoma and the VPN client, then updating to the beta. If it worked on Sonoma and then breaks with the upgrade to the beta, then you know it isn’t going to work.
What worked for me is enabling the secure client socket filter under System Settings > General > Login Items and Extensions > Extensions > Network Extensions
Full version released of Mac OS 15 yestorday, any issues? I am having some issues with dropouts to git server while on vpn. Also there might be some issues with resolving other services too. Any one else experience this, I uninstalled and re-installed the latest vpn client to get all the options re comfirmed properly… but still it seems a bit unstable.
Sequoia release on Monday, I updated to 15.0 on a new Mac, for deployment. and the request to allow the network socket filter wouldn’t show up. I was wondering if Cisco wasnt’ notrised, and was looking at rolling back the OS. This ^ saved me. Thanks