Hello, I have a Hyper-V Core server running 2016 as a VM, and I can't access the Internet. I was running everything successfully last night, and wiped the server down to metal to make sure the instructions were correct, and it looks like I missed documenting one step. Nevertheless, it means it's not a hardware issue.
The problem is that when loading MS2016, I can not get an Internet connection. (The problem is also true with 2012 and Ubuntu 16.10, which leads me to believe this is in the way the virtual switch is configured.)
On the host HV:
13 192.168.43.222 Hyper-V Virtual Ethernet Adapter
Select Network Adapter Index# (Blank=Cancel):
and ipconfig /all (with the extraneous junk cut out)
Ethernet adapter Ethernet 3: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : QLogic BCM5709C Gigabit Ethernet (NDIS VBD Client) #56 Physical Address. . . . . . . . . : 64-31-50-4E-46-B0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::31c6:9d08:694f:35a8%5(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.43.200(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.43.1 DHCPv6 IAID . . . . . . . . . . . : 191115600 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-D3-BB-F2-64-31-50-4E-46-B2 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter vEthernet (Emulated Internet): Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter Physical Address. . . . . . . . . : 64-31-50-4E-46-B4 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::ada6:b54c:d2a1:d919%42(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.43.222(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Friday, December 2, 2016 7:07:36 PM Lease Expires . . . . . . . . . . : Tuesday, January 9, 2153 1:48:37 AM Default Gateway . . . . . . . . . : 192.168.43.1 DHCP Server . . . . . . . . . . . : 192.168.43.1 DHCPv6 IAID . . . . . . . . . . . : 711209296 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-D3-BB-F2-64-31-50-4E-46-B2 DNS Servers . . . . . . . . . . . : 192.168.43.1 NetBIOS over Tcpip. . . . . . . . : Enabled
And in the Hyper-V Manager, the Virtual Switch is set to "External", and I am definitely using the right card (#58) to link to the switch. I have tried checking and unchecking all the boxes and rebooting all the hardware, both the VMs and the physical server. Here's the current configuration: http://imgur.com/I8ppTW7
And as I have read several guides suggesting that I cycle the option boxes, I want to make it clear that I have cycled all the option boxes.
I have turned the firewall on the Hyper-V server completely off for troubleshooting.
Since I'm posting this, it's not a problem with my router and I can see that there is no VM on the client list.
ipconfig from the VM is here. As you can see, it's still using the default address.
Ethernet adapter Ethernet 3: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : QLogic BCM5709C Gigabit Ethernet (NDIS VBD Client) #56 Physical Address. . . . . . . . . : 64-31-50-4E-46-B0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::31c6:9d08:694f:35a8%5(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.43.200(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.43.1 DHCPv6 IAID . . . . . . . . . . . : 191115600 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-D3-BB-F2-64-31-50-4E-46-B2 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter vEthernet (Emulated Internet): Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter Physical Address. . . . . . . . . : 64-31-50-4E-46-B4 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::ada6:b54c:d2a1:d919%42(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.43.222(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Friday, December 2, 2016 7:07:36 PM Lease Expires . . . . . . . . . . : Tuesday, January 9, 2153 1:48:37 AM Default Gateway . . . . . . . . . : 192.168.43.1 DHCP Server . . . . . . . . . . . : 192.168.43.1 DHCPv6 IAID . . . . . . . . . . . : 711209296 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-D3-BB-F2-64-31-50-4E-46-B2 DNS Servers . . . . . . . . . . . : 192.168.43.1 NetBIOS over Tcpip. . . . . . . . : Enabled
Neither a restart on the VM nor an ipconfig /renew seems to do anything except throw a "could not reach the DHCP server" error. (Similar error with different text to the Ubuntu Server when setting that up.)
What am I missing here? Last night nothing worked until I installed MS2012, and then mysteriously both 2016 and Ubuntu Server were 100% fine. That didn't fix anything this time.
Any help you can throw my way would be excellent.
Thanks!