Jump to "UPDATE" below for new information. It was an unpleasant surprise to discover that 2-4 did not seem to be handled by the above changes. They are under "Inbound Rules" and called "File and Printer Sharing (Echo Request - ICMPv4-In)" By using a virtual adapter installed by VMWare there are no changes made to your real adapters and therefore fewer edge cases where it causes disruptions to other networking activities on your Win 8.1 Hyper-V host.īy the way, if you are hoping to use ping to verify your connections, you will need to enable ICMP echo firewall rules on any of the real or virtual machines you wish to respond to ping. So that solves #1 nicely! The article is here: and includes simple commands to temporarily disable Hyper-V.Ĭonfiguring a Hyper-V switch against a physical adapter on your system causes Hyper-V to own that adapter. Then you configure a Hyper-V switch to connect to Vmnet8 - which is a NAT / DHCP segment that gives your VMs seamless access to the internet, no matter what the host configuration is. Essentially you disable Hyper-V with a boot configuration, install vmware player and then re-enable hyper-v. So the first bullet is adequately answered by the blog post of Thomas Vochten (and others).
This becomes manual fussing around in Hyper-V everytime you use a different network. Dynamic NAT for all VMs to connect to the Internet, no matter how my laptop happens to be connected at the moment.
So what did I lose, that I would like back when using Hyper-V networking? Here's the list: But in the meantime, I have some steps to make this as easy as possible. Hey Microsoft, you really should do something about this since I see it cited ad nauseam as a primary reason many IT Pros retreat from their attempt to adopt Win 8 Hyper-V and go back to VMware. Wow - sometimes you don't know how easy you've got it until you step off the cliff! That cliff for me was attempting to replace VMware Workstation with Windows 8 Hyper-V.
0 kommentar(er)
