I have a small Hyper-V host (created and configured by a prior admin), running Server 2012. It has 4 physical NICs, one used for management, a second connected to an External Virtual Switch, and the other 2 disconnected.
There were two existing VMs running under the host: a Windows AD and a Windows File Server. Both have no trouble talking to the host, or to the outside world, and vice-versa. I am trying to add a third VM, but I cannot get it to talk beyond
the Virtual Switch.
I have checked the settings on the individual VM configurations, and everything I can see on the Virtual NIC is the same for all three VMs. They are all bound to exactly the same External Virtual Switch, and everything looks the same.
The major difference in the new VM is that it is a CentOS Linux VM. However, I have done this same thing on a larger Hyper-V host (one hosting more than a dozen VMs), with both CentOS and Ubuntu with no problems. I have compared setups between
the two different Hyper-V hosts and they are essentially identical to my understanding.
For this new VM, I first tried version 7 of CentOS, but when that didn't work fell back to version 6, which I had successfully used on the larger host. No joy. I have tried both manually assigning IP configs and using DHCP. The new
VM happily gets an IP by DHCP from the Windows AD server. Whether manual or DHCP, it cheerfully talks to the AD and File Server which are on the same virtual switch. But it absolutely will not talk to the Host or to the outside world. Routes
and gateway configurations all look right. Just... silence.
Almost certainly I have missed something simple, but *what*?