Skip to content
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

Bash on Ubuntu for Windows has no connectivity. Reinstalled multiple times. #1725

Closed
Todai88 opened this issue Feb 24, 2017 · 3 comments
Closed
Labels

Comments

@Todai88
Copy link

Todai88 commented Feb 24, 2017

As with many other people I'm completely unable to run any network functions; neither cURL, ping or any package updates (sudo apt-get update).

I've tried many of the suggested changes in other threads (running bash with elevated priviligies, adding nameserver 8.8.8.8 in /etc/resolv.conf etc), but nothing seems to work.

I should mention that I'm running BullGuard AV, but I've attempted to turn off both the Windows Firewall and BullGuards bundled Firewall. Again, doesn't work.

  • Expected results

Clearly I want bash to work as intended, where I can curl servers etc.

  • Actual results (with terminal output if applicable):

sudo apt-get update gives me

Err http://archive.ubuntu.com trusty InRelease

Err http://security.ubuntu.com trusty-security InRelease

Err http://archive.ubuntu.com trusty-updates InRelease

Err http://archive.ubuntu.com trusty-backports InRelease

Err http://security.ubuntu.com trusty-security Release.gpg
  Could not resolve 'security.ubuntu.com'
Err http://archive.ubuntu.com trusty Release.gpg
  Could not resolve 'archive.ubuntu.com'
Err http://archive.ubuntu.com trusty-updates Release.gpg
  Could not resolve 'archive.ubuntu.com'
Err http://archive.ubuntu.com trusty-backports Release.gpg
  Could not resolve 'archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/InRelease

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-updates/InRelease

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-backports/InRelease

W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/InRelease

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release.gpg  Could not resolve 'archive.ubuntu.com'

W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/Release.gpg  Could not resolve 'security.ubuntu.com'

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-updates/Release.gpg  Could not resolve 'archive.ubuntu.com'

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-backports/Release.gpg  Could not resolve 'archive.ubuntu.com'

W: Some index files failed to download. They have been ignored, or old ones used instead.

And ping www.google.com gives me:
ping: unknown host www.google.com

Finally ping 8.8.8.8 gives me:
Do you want to ping broadcast? Then -b

  • Your Windows build number

image

  • Steps / All commands required to reproduce the error from a brand new installation

In my case, absolutely nothing. I've removed and installed the Bash service twice with no changes.

  • Strace of the failing command
  • Required packages and commands to install

See our contributing instructions for assistance.

@aseering
Copy link
Contributor

Hi @Todai88 -- as you mention, a number of people have experienced this issue; it has actually turned out to have many different unrelated causes, and often (though not always) with a root cause of a misconfigured network or buggy third-party Windows security application. So it may be worth your time to dig through more of the existing resolved tickets to see if their resolutions help you. (It would be great if WSL provided a debugging wizard or something to help catch the common cases; alas, this doesn't exist to my knowledge.)

One thing immediately jumps out at me: Has anyone verified that BullGuard AV works with WSL? I'm not familiar with it. I know you've turned it off. But a lot of early WSL users had problems where their antivirus or firewall software blocked WSL even when it was turned off. The only fix was to uninstall, or to upgrade to a fixed version of the security software once one was released.

@sunilmut
Copy link
Member

sunilmut commented Mar 3, 2017

@Todai88 - You can also try deleting your /etc/resolv.conf, closing and reopening bash again, and see if that makes any difference.

@tara-raj
Copy link

Please try this on a more recent Windows Build (EX: 1803) and please reopen if you still run into this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants