Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have just installed a new Hyper-V host machine running Server 2008 R2. Created the first VM (also Server 2008 R2 SP1) and all is working apart from a bizare problem with network packets.

Host machine has two Intel Nic's one is dedicated to Hyper-V and is setup as an "External" network in Virtual Network Manager. It's also removed from the management OS, so dedicated just to Hyper-V. (We have two other Hyper-V hosts with the exact config).

The guest machine was installed and connected to this virtual network, but the guest OS can not receive network packets, it only sends. I configured a manual static IP but still nothing.

It has however managed to pick up an IPv6 address from one of our routers that hands them out, pinging the address does not work and I am unable to ping IPv6 addresses from the guest machine.

Suggestions? I have double checked as many settings as I can think of compared to our other hosts, but this is just weird!


share|improve this question
up vote 0 down vote accepted

Removing the Hyper-V role and adding it again resolved this problem. I also reinstalled the guest O/S.

I would have liked to figure out what was actually broken!

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.