[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.] So how's that networking do-dads work in HyperV anyway? - THE OFFICIAL BLOG OF THE SBS "DIVA"
Thu, Dec 4 2008 22:59 bradley

So how's that networking do-dads work in HyperV anyway?

Virtual PC Guy's WebLog : Understanding Networking with Hyper-V:
http://blogs.msdn.com/virtual_pc_guy/archive/2008/01/08/understanding-networking-with-hyper-v.aspx

So how does this networking stuff work in HyperV anyway?

I've found I will build a box with a legacy nic, the server will install and then after it's builtI will flip it to a "synthetic nic" as it's called.

My hyperV box has two physical network cards, one is connected to my duplicate router.  As you can see once the HyperV role is enabled I now have four network connections.  The reason is that I have two virtual networks setup to hold the network topologies I have set up.

I'll blog more on this later as well as I'm still getting a handle on this myself in the meantime read -- Hyper-V Getting Started Guide:
http://technet.microsoft.com/en-us/library/cc732470.aspx

After you install Hyper-V and create an external virtual network, your computer will operate differently. After installation, the parent partition uses a virtual network adapter to connect to the physical network. When you look at Network Connections on the parent partition, you will see the original network adapter and a new virtual network adapter. The original physical network adapter has nothing bound to it except the Microsoft Virtual Network Switch Protocol, and the virtual network adapter now has all of the standard protocols and services bound to it. The virtual network adapter that appears under Network Connections will have the same name as the virtual network switch with which it is associated. It is possible to create an internal virtual network, which will expose a virtual network adapter to the parent partition without the need to have a physical network adapter associated with it. Hyper-V only binds the virtual network service to a physical network adapter when an external virtual network is created. However, networking will get disrupted for a short period of time on the network adapter when a virtual network gets created or deleted.

The part I need to still understand and investigate more is how to have a single nic SBS box not be hooked to the physical network adapter.  That's the part that I'm not quite gelling in my mind of how the magic works.  Stay tuned.

Filed under:

# re: So how's that networking do-dads work in HyperV anyway?

Friday, December 05, 2008 12:57 PM by Philip Elder

You can do it one of two ways:

Method #1:

SBS 2008 NIC is setup to an Internal virtual network (we name it SBS 2008)

Win2K3 with ISA installed on another VM with 2 NICs (one SBS 2008 and one tied to External).

ISA provides the break between the internal SBS 2008 virtual network and access to the Internet via ISA.

Method #2:

SBS 2008 NIC is set up to connect to a dedicated host NIC.

Dedicated host NIC is plugged into a dedicated switch (router or appliance connected to switch too).

There are other methods of working it out, but the above provides us with enough flexibility for our hosting environments to scale up when needed.

Philip