search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.04k stars 797 forks source link

WSL2: Cisco anyconnect not connecting after running wsl --update #9561

Open kodergeek opened 1 year ago

kodergeek commented 1 year ago

Hi,

I have been using wsl2 for several months now on windows 11 and my guest OS is Ubuntu (Linux 5.15.79.1-microsoft-standard-WSL2)

I recently got a prompt when starting Ubuntu console about WSL now being available on Microsoft Store and the prompt indicated I can simply run wsl --update to update to the new WSL. So all I did was to run this command. After performing this update, I can no longer connect to VPN using Cisco Anyconnect. I did not change anything else (like updating Ubuntu or Cisco Anyconnect client) Now I am getting this error:

VPN establishment capability for a remote user is disabled. A VPN connection will not be established

I have verified that I can connect to same VPN portal using both Windows and other stand alone Linux laptop, and even another Ubuntu running using Virtual box, So the VPN server is working fine for other Linux and windows clients.

WSL version: 1.0.3.0 Kernel version: 5.15.79.1 WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 anyconnect-linux64-4.10.06079 Windows version: 10.0.22621.1105

frivard-coveo commented 1 year ago

I have a similar issue.

After I did the wsl --update prompt to use the Store version, my VS Code no longer see any distro and doesn't work in WSL mode anymore. And today after I did a Docker Desktop update to the latest version, it refused to start so I had to competely reset it; it works on Windows, but on the WSL Integration page, it also says that I don't have any WSL 2 distro installed. (which is not true, I have Ubuntu 22.04 installed and it's working fine).

So after the wsl --update, there are two different programs which say that I don't have any WSL 2 distro installed.

ghost commented 1 year ago

@frivard-coveo, What version of wsl are you running wsl --version?

frivard-coveo commented 1 year ago

What version of wsl are you running wsl --version?

❯ wsl --version
WSL version: 1.0.3.0
Kernel version: 5.15.79.1
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1105
MirChamb3r commented 1 year ago

I'm in the exact same situation as well, updated to the windows store version for WSL2 and now the cisco anyconnect software gives the same error. However, this only occurs when I enable systemd in the wsl.conf file. Whenever I disable it and start a few services manually it connects fine again.

So I think WSL2 could now be starting (or possibly registering) something that then blocks the VPN from being established.

DarkVen0m commented 1 year ago

Same issue here on WSL 1.1.3.0

davidroth commented 11 months ago

Just experienced the exact same issue because I set up a new laptop where I installed WSL via the store.

However, this only occurs when I enable systemd in the wsl.conf file. Whenever I disable it and start a few services manually it connects fine again.

@MirChamb3r

Thanks, that did the trick for me as well! Setting the systemd config in /etc/wsl.conf to false and then wsl --shutdown did work.