External Virtual Network
Virtual machines connected to an external virtual network are given access to the external network via a physical network adapter installed in the host system. Virtual machines are also able to communicate with both the parent partition and other virtual machines running on the same virtual network.
Internal Virtual Network
Virtual machines connected to an internal virtual network have access to both the parent partition and other virtual machines attached to the same virtual network. Hyper-V Internal Virtual Networks do not require a physical network adapter and no access to external networks is provided.
Private Virtual Network
Virtual machines connected to a private virtual network have access only to other virtual machines attached to the same virtual network. Hyper-V private virtual networks do not require a physical network adapter and no access to the parent partition or external network is provided.
http://www.virtuatopia.com/index.php/Understanding_and_Configuring_Hyper-V_Virtual_Networks----------
As one of your NICs are connected to your home router / switch and you are able to browse the internet from the host - good.
Now, connect the 2nd NIC as well to your Home router / switch (ethernet - lan port)
Follow the screen shots, setup a new virtual network, and use your 2nd NIC, make sure the type is set to "External"
This will enable your virtual machines to appear as physical computers / servers on your Local LAN
they will have the same subnet as your router, physical host box as well
you don't have to assign a static ip to your 2nd NIC to start with and once the Hyper V network protocol switch binds itself to it, you will see no ip on it, it will act as a switch and your vms would have IP Addressess of the same subnet as your host / router. You can assign static or dynamic ips to your vms.
