As I found, the client modifies route connections in wsl interface, making it no longer able to connect to internet. More info at https://wheatevo.com/wsl-2-and-vpn/ I modified a bit the script in that web so we delete the vpn new rule and re create the old route rule: NOTE: In my PC Pulse secure network is called "Ethernet 3", that may not be your case. Check with Get-NetAdapter in powershell console.   With this script i am able to connect to the internet (8.8.8.8 for example) and to the VPN network.   PowerShell script need elevated privileges:   $wsl = Get-NetIPInterface -InterfaceAlias "vEthernet (WSL)" -AddressFamily IPv4 $vpn = Get-NetIPInterface -InterfaceAlias "Ethernet 3" -AddressFamily IPv4 $ip = Get-NetIPAddress -InterfaceAlias "vEthernet (WSL)" -AddressFamily IPv4 $networkIp = "$($ip.IPAddress -replace "\.\d+$", ".0")" route delete $networkIp IF $vpn.ifIndex route add $networkIp mask 255.255.240.0 0.0.0.0 IF $wsl.ifIndex   ... View more

I Will tell you one solution that works for me.  -Before get connected to the VPN: Disable vEthernet (WSL) network connection. -Connect to the VPN (This will create the interface Pulse Secure) -Enable vEthernet (WSL)   With this steps i am able to connect to IPs inside vpn network from WSL and i am able to navigate trough the internet also inside WSL ... View more