05-11-2021 01:52 AM - edited 05-11-2021 01:54 AM
I'm using Cisco AnyConnnect V4.8 as my VPN running Ubuntu 20.04 on my Dell latitude 5490 laptop. My VPN connects then disconnects every 5 minutes. Depending on the network sometimes the connection will stay longer periods of time when hardwired directly with ethernet wire but the problem still persists. I've been running into this problem ever since switching to Ubuntu 20.04 from Windows 10. Any help would be much appreciated! Thank you!
Solved! Go to Solution.
05-11-2021 10:06 PM
We have seen this problem on Ubuntu 20.04 if NetworkManager (NM) is on. Please test establishing VPN after disabling NM from Settings>Privacy>Connectivity.
Regards/Saurabh
05-11-2021 02:10 AM
- Check /var/log/messages when this happens (or around those time-frames), check if anything useful can be observed.
M.
05-11-2021 03:06 AM
While Windows 10 is your connection was ok?
Look at the below suggest thread :
https://community.cisco.com/t5/vpn/anyconnects-reconnecting-problem/td-p/2850760
https://community.cisco.com/t5/network-access-control/anyconnect-keeps-reconnecting/td-p/3482440
05-11-2021 06:43 PM
check MTU of your SP.
05-11-2021 10:06 PM
We have seen this problem on Ubuntu 20.04 if NetworkManager (NM) is on. Please test establishing VPN after disabling NM from Settings>Privacy>Connectivity.
Regards/Saurabh
05-11-2021 10:45 PM
This worked! Thank you so much :)!!
08-15-2023 05:34 PM
This solution doesn't work in either Ubuntu 20.04 or Ubuntu 22.04. Any other suggestions? I'm facing this issue in Ubuntu 22.04.3 LTS with Cisco Anyconnect (4.10.04071) downloaded from cisco
08-15-2023 07:51 PM
Solved it. Disabling connectivity manager will not fix it. You have to remove it altogether in Ubuntu
sudo apt-get remove network-manager-config-connectivity-ubuntu
Fixed it for me. 10minutes so far and no network retries or drops!
04-13-2024 07:05 PM
This works for me. Thank you!
02-20-2025 07:55 AM
WARNING: Disabling and/or removing the network manager does fix the problem (at least for me), but it has a side-effect. When the system is rebooted, the network will not come back up (because there is no network manager to manage it), so the system comes up with no network. In order to resolve the issue, you now have to start the network manually using these commands (as root):
$ ifconfig <interface> up
$ dhclient <interface>
I just scripted these and added them to the system startup
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide