0

I created an Ubuntu 18.04.1 LTS VM using Hyper-V Quick Create on Windows 10 Pro Version 1803. It seems to have worked except I am not able to access websites with http. Name resolutions seem to be working fine. I am able to ping addresses, but accessing websites with Firefox always times out.

Ping:

ping capture

When I attempt to telnet to port 80:

telnet capture

My network connection icon shows as a question mark:

network icon capture

My wired connection details:

Wired settings

slava
  • 3,787
  • 9
  • 30
  • 65
Dan Lauterbach
  • 1
  • 1
  • 2

1 Answers1

0

It seems likely that the IP addresses are being used by multiple systems. For example, if you're using a static IP address on multiple machines.

Kristopher Ives
  • 5,419
  • 2
  • 27
  • 36
  • @krisives - Not sure how this could be the case. I don't believe I'm using static IPs. Ubuntu is running as VM on top of Windows 10 and I believe somehow uses NAT to allow Ubuntu network access through the Windows NIC. I can access the internet fine from Windows 10. – Dan Lauterbach Dec 31 '18 at 00:19
  • Are you running multiple VMs? – Kristopher Ives Dec 31 '18 at 00:21
  • See https://askubuntu.com/questions/515391/unable-to-connect-to-internet-on-hyper-v-ubuntu-14-04 – Kristopher Ives Dec 31 '18 at 00:24
  • No. I've created two VMs in an effort to resolve, but only running one currently. – Dan Lauterbach Dec 31 '18 at 00:25
  • @krisives - I tried every variation of the solution in your link that I could think of. I tried both bridging my WiFi and my Ethernet connections. I tried bridging newly created virtual switch as well as the out-of-the-box "Default Switch". Bridging my WiFi while Windows was using Ethernet produced same result, can ping but cannot telnet to port 80. Bridging Ethernet insted of my WiFi connection resulted in Windows losing connectivity and Ubuntu not being able to start the interface. – Dan Lauterbach Dec 31 '18 at 20:01
  • I don't use Hyper-V but VirtualBox instead and don't have this problem, but I can tell you that it's something to do with Hyper-V or your networking configuration because your `ping` command shows that google.com is resolving to an IP address within that subnet, which is incorrect. – Kristopher Ives Dec 31 '18 at 21:55
  • I agree both my local IP and the resolved google.com IP address begin with 172 but the IP address for google.com is not on my local subnet. If I ping google.com from Windows 10 (the host) I get same IP address. I do not understand why ping works but I cannot access any addresses over port 80. I've been using VirtualBox but I'd like to switch to Hyper-V as I think it will be faster and VirtualBox conflicts with Docker as Docker (on Windows 10) requires that Hyper-V be enabled. Thank you for your ideas. I really want this to work. – Dan Lauterbach Jan 02 '19 at 04:55
  • Turns out the reason I was not able to access the internet was due to Symantec Endpoint Protection (SEP) software installed on my Windows 10 host. SEP was blocking external access to all ports on my Windows 10 host and SEP was seeing my VM as external. Since I am running this on my employer provided laptop I would have to make a strong case for running a unique SEP policy. I switched back to using VirtualBox and do not have this problem. Drawback is Ubuntu runs slower on VirtualBox than Hyper-V. – Dan Lauterbach Jan 08 '19 at 02:24