Hyperv and the Virtual switching - Vm's unable to access internet

https://community.spiceworks.com/topic/466370-event-id-2-hyper-v-netvsc-error-vm-and-host-failed-to-negotiate-protocol-v-5-0

Sonora
dbelleba Feb 19, 2016 at 7:02 PM
@ bevege (I realize hes probably not here but for anyone else who had problems like his I ran into the same thing not too long ago).



Theres a known bug with Hyperv and the Virtual switching. You can tell this if you've double checked everything and your vms get local traffic but no internet and your vm host gets local and internet or your vm host doesn't get internet but your vms do. So it basically one or the other.



The fix?



On the virtual switch uncheck the box that says "allow management operating system to share this adapter". Hit apply. Ok. Open it back up, recheck it, hit apply, ok. Whola fixed.

The bug is that when its preselected when the switch is created it doesn't apply correctly. So by rechecking it, its like a refresh. I spent about 4 hours network troubleshooting getting ready to rip the roof off and came across a bug report.



Anyone find a fix for the server 2012 vm hosts adding additional domain controllers in server 2012 R2 and getting stuck on NTDS installation?

Thanks!

Was this post helpful?
 Spice Reply

Pimiento
quirinocardozo Feb 21, 2016 at 4:13 PM 1ST POST
Hi all, after much head-banging, reading up everyone's frustrating stories and all of the R&D attempted, and almost at the verge of giving up and re-building the whole VM Host and VMs back to 2008 R2, dbellba's post above gave me a hint where to look.

- Although I could not find the "virtual switch" he's referring to, I did have a "Virtual Network Manager", which when I investigated displayed the name of the Host's NIC plus a "#2" extension to it.
- Below in the "Connection type", I tried selecting the main NIC that was physically connected to the LAN cable, received a warning that I would be temporarily disconnected - which I was, re-connected via VM-Host's IP
- Then after re-connecting, did a re-boot of the VM.

Guess what? It worked!!! My stubborn 2012 R2 VM's online now.

Hope this helps (and works!) for anyone else out there.

Found on Spiceworks: https://community.spiceworks.com/topic/466370-event-id-2-hyper-v-netvsc-error-vm-and-host-failed-to-negotiate-protocol-v-5-0?utm_source=copy_paste&utm_campaign=growth

https://community.spiceworks.com/topic/466370-event-id-2-hyper-v-netvsc-error-vm-and-host-failed-to-negotiate-protocol-v-5-0

Windows 7 won't boot up after install on Hyper-V

https://social.technet.microsoft.com/Forums/systemcenter/en-US/f324ff98-25ba-4732-87a6-1dada4e8b5e4/windows-7-dont-boot-after-install-hyperv

Okay, I am ABSOLUTELY SHOCKED after a ton of web searching that an incredibly SIMPLE solution to this problem exists, but no one on any of these forums seems to be capable of understanding and revealing the answer... SO -- here it is:

1. Create a new Virtual Machine on your Hyper-V (Server 2008 R2).
2. Install Windows 7 from a DVD or an ISO file, whatever makes you happy.
3. On the final reboot of the install, you will, of course, get the above mentioned black screen.
4. Reboot the VM, but this time press a key to boot from the Windows 7 DVD (or boot from your ISO) so that you can get into the repair mode (recovery console/DOS prompt).
5. Type C: to go to the C (boot) drive of your Windows 7 VM.

Here's the magic:

6. Simply type the following command at the recovery console DOS prompt:

bootsect.exe /nt60 all /force

7. type EXIT and then reboot the machine.

ENJOY!

• Proposed as answer by Eric D Madsen Friday, January 21, 2011 3:44 PM
• 
  

https://social.technet.microsoft.com/Forums/systemcenter/en-US/f324ff98-25ba-4732-87a6-1dada4e8b5e4/windows-7-dont-boot-after-install-hyperv