Windows 2012 Datacenter R2 - Network Connections Confusion

Question

I have recently created a 2012 Datacenter install with the goal to create virtualize test lab. 
As part of the install two connections were created:
1. Labeled 'Ethernet' with Hyper-V Extensible Virtual Switch protocol enabled.
2 Labeled 'Network 2' vEthernet (....Controller - Virtual Switch) with the standard networking protocols enabled.
3. Network 2 interface is connected to the local area network.
Ethernet adapter vEthernet (Realtek PCIe GBE Family Controller - Virtual Switch):
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
Physical Address. . . . . . . . . : BC-5F-F4-3B-11-EE
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled
I am confused with the purpose of the network connection "Ethernet" and Hyper-Virtual Switch protocol and how this relates the "network 2" interface. I uncertain which network connection is the physical connections.
I have tried to research this with "windows 2012 datacenter network connection configuration, setup, and etc.",  the results are a lot of the complex examination of setting of Hyper-V implementation, clusters, DHCP, and etc.
I hoping to locate information that will explain the fundamentals of these related technologies (tutorial, youtube videos, etc.).  Any helpful advice is welcome.

Answer 1

Hi,
Based on the information which you provide, you created an External virtual switch, which binds to the physical network adapter so that virtual machines can access a physical network.
->I am confused with the purpose of the network connection “Ethernet” and Hyper-Virtual Switch protocol and how this relates the “network 2” interface. I uncertain which network connection is the physical connections.
->Network 2 interface is connected to the local area network.
Based on your description, I suppose that you encountered some problems with understanding virtual network switch. When we install Hyper-V and create an external virtual network, the management operating system uses a new virtual network
adapter to connect to the physical network. The network connections consist of the original network adapter and the new virtual network adapter. The original physical network adapter does not have anything bound to it. However, the virtual network adapter
has all of the standard protocols and services bound to it. Here, the “vEthernet” is the new virtual network adapter, and the “Ethernet” was the original physical network adapter. Hyper-V binds the Virtual Network Service Protocol to the physical network adapter
when an external virtual network is created. So the “Ethernet” has the Hyper-V Extensible Virtual Switch only. The physical adapter was equal to a virtual switch at this moment, all networking traffic is routed though the virtual switch.
And to the physical machine, due to the physical adapter is a virtual switch now, so the new virtual network adapter is its network adapter now. So we can see the all TCP/IP configurations of vEthernet are the same with the local area
network.
For more details about virtual network switch, please refer to the link below,
http://technet.microsoft.com/en-us/library/dd581798(v=WS.10).aspx
Best Regards,
Tina