WSL Terminal can't ping but CMD can ping and SSH. Internet unaffected

[as226855]

So With VPN off, my WSL terminal can ping/ssh, but as soon as I turn on VPN, terminal cannot ping/ssh but CMD can. Here is a screeenshot. Can you please help me with this issue? I searched a lot but did not find a solution. The small terminal on the left is WSL and the large terminal on the right is CMD.

[Marius Gunnerud]

So when AnyConnect is connected you cannot ping from WSL but CMD is able to ping? 

• Is the AnyConnect VPN running tunnel-all traffic? or Split-tunnel?  
• What DNS is the WSL using compared to your PC's DNS?

[giovanni.augusto]

As far as I can see on my own WSL2 VM I am experiencing the same behavior, from a quick search online I can see many other people does too.

Personally I can tell that this happens to me with a VM using WSL2 version, if you switch to WSL1 most likely it will work as the network stack is different.

If you want a potential solution for your problem you can look into this specific topic from WSL github page: https://github.com/microsoft/WSL/issues/4731#issuecomment-1203643323

I haven't tried it but you may and let us know.

[Marvin Rhoads]

I have seen clients with issues using WLC + VPN due to the VPN client not updating WLS's DNS settings. Their work around was to manually change the DNS settings in WSL when connected to VPN.