Hyper-V on Windows 8 Pro: Unexpected error while configuring network. What's wrong?

Question

Virtualization

Created a virtual machine in Hyper-V, created a virtual switch. The Hyper-V network adapter has appeared in the guest OS and the main OS. Read here that the network bridge should be created. But I can't set up a bridge with a real network card.
The fact is that as soon as I create a virtual external switch, all protocols and the IP address disappear from my real network card, only the Hyper V protocol remains.

And at the same time, the Internet naturally disappears on a real computer. Can you suggest where to dig? Another nuance - the main computer receives the Internet via pppoe (cord to the system unit, without routers). I tried everything - still the same error: pppoe stops connecting as a class. Either it always checks accounts, or it falls into an error, unlike tutorials, where they write that everything rises by itself, like clockwork. CHADNT?

Answer 1

So, first you need to understand what vSwitch is and how it works.
As soon as you enable the virtualization option for a network card, Windows removes all protocols and services from it, and also makes the physical card unavailable for traffic for all systems - both guest and host. After that, depending on the checkbox in the properties of the switch, a second network card is created that is available to the host machine, all the necessary protocols and services are hung on it.
In your case, this is exactly what is happening. The physical card has become unavailable and is, as it were, one port of the virtual switch and looks "from the system unit", and the second created card is another port of the virtual switch, which, as it were, "looks" at the host operating system.
Farther. PPPoE connection does not use IP addresses for operation and all that is needed is only the "Client for Microsoft Networks" service, focusing on the interfaces in which this service is activated (checked), and a connection is established
(broadcast "Hey, there is a server here that can me accept", the response from the server is "Here I am, give me the details", the client's response to this is "Yes, ok?" oh well, give traffic here", after that connect).
In your case (not visible from the screenshots), there may be an error in the firewall, there is no checkbox in the service, or in the settings in the Switch there are checkmarks ("allow traffic somehow" - quarrel with me in the English version, google the exact wording or just orient yourself) do not There is also a second card - this is some other switch, and not the one that is connected to the physical card.
There is another option that you have enabled any Vlan in the switch properties - if so, then, of course, you need to turn it off.