-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot ping both from Windows host and WSL #8462
Comments
I just ran into the same issue, the problem was I had my VPN on. |
I've found this to be the root of the DNS issues on my system too. The system ...
Here is the complete set of symptoms.
If I disconnect the ZScaler from the company network (Private Access - Turn Off) then all the pings and resolving hostnames work correctly. However, this is a workaround that is very is not workable in practise as I, and all the people I'm responsible to create dev systems for (100 scaling to 1000), have to be able to work with the company VPN connected. |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Version
Microsoft Windows [Version 10.0.22000.675]
WSL Version
Kernel Version
5.10.102.1
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
IP addresses of Windows host:
IP address of WSL:
Use ping from Windows host to WSL and vice versa.
Expected Behavior
Ping successful.
Actual Behavior
Pinging from Windows host:
Pinging from WSL:
WSL can connect to the Internet (pinging 8.8.8.8, google.com, apt update,...all good)
/etc/resolv.conf:
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: