This is driving me crazy and I've spent a little too long of a vacation trying to figure thus out. But since this vacation was a chance for me to make some progress on a non-work project - well, it's really bugging me (and is a blocker I've had for two days so far)! Any help would be appreciated.
I am running HyperV on a Windows 8.1 host. I need to create a guest that has internet access. Just to remove any questions as to whether my hardware and OS installation support this, I had this working perfectly last week on the exact same machine. I simply added an external network through the HyperV Virtual Switch Manager, added that under Settings -> Network for the VM in question and everything just worked immediately. The guest obtained an IP address just fine and all was rosy.
So, then I come on vacation and set up a VM. I'm on a different physical network but everything seems the same from the host perspective - I just connected to the wireless network and the host itself works just fine.
However, no matter what I try I can't get the guest VM to obtain an IP address. I've done the same configuration with the external virtual switch, bound (in Settings -> Network) to the VM and so on. The VM sees the virtual NIC card just fine - but always fails to obtain an IP address (can't reach the DHCP server, I believe).
The only thing that has changed - as far as I know - is the network environment. The new environment immediately and easily supported me getting the host hooked up (it got an IP address itself) and provides access to the Internet.
By the way, I did see some recommendations to create an INTERNAL virtual switch and bridge with the wifi connection. I don't know why that would be preferred over the more direct use of an external virtual switch - but, regardless, that approach failed too (same issue - no response from DHCP server).
Any ideas on what might be going on here?
Thanks in advance.
Mark Williams