> Hopefully someone can explain this to me. I have two physical NICs on a
> server. In Hyper-V Manager I assign one of them to a virtual server. The
> NIC I assigned to the virtual server created a Local Area Connection -3and
> has Microsoft Virtual Network Switch Protocol checked. The NIC that was
> not assigned to the virtual server has a static ip of 192.168.1.4. Inside
> the virtual server I assigned 192.168.1.2 but outside the vitual server it
> is set to dynamic and picked up 192.168.1.22. I don't understand the role
> of the NIC with the dynamic IP. Should I be assigning a static IP to it
> and what is it used for?
>
> From another computer on the same network I tried to ping the host
> 192.168.1.4 but couldn't. I could ping 192.16.1.22. I need to make sure
> that I can always connect to the host for managing.
>
> -courtk

>
>
> "CourtK" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Hopefully someone can explain this to me. I have two physical NICs on a
>> server. In Hyper-V Manager I assign one of them to a virtual server.
>> The NIC I assigned to the virtual server created a Local Area
>> Connection -3and has Microsoft Virtual Network Switch Protocol checked.
>> The NIC that was not assigned to the virtual server has a static ip of
>> 192.168.1.4. Inside the virtual server I assigned 192.168.1.2 but
>> outside the vitual server it is set to dynamic and picked up
>> 192.168.1.22. I don't understand the role of the NIC with the dynamic
>> IP. Should I be assigning a static IP to it and what is it used for?
>>
>> From another computer on the same network I tried to ping the host
>> 192.168.1.4 but couldn't. I could ping 192.16.1.22. I need to make sure
>> that I can always connect to the host for managing.
>>
>> -courtk
>
> First up, you do not assign NICs to virtual servers in Hyper-V. You
> create virtual switches assigned to NICs. You then join the NIC in a vm to
> the virtual switch.
>
> I agree that this is confusing. The best explanation I know of comes
> from Ben Armstrong's blog.
>
> http://blogs.msdn.com/virtual_pc_guy/archive/2008/01/08/understanding-networking-with-hyper-v.aspx
>
> This process has been improved in R2, but that is not really much help
> for you!
>
> What do you want your network to do? If you do not want the OS in the
> parent partition to use this NIC, clear all the check marks from the boxes
> in the new properties sheet. Leave the MVNSP box ticked it the other
> properties sheet. This NIC is then dedicated to the virtual switch, and
> will not have an IP in the parent partition.
>
> If both the NICs are plugged into the same physical switch, you should
> now be able to communicate between the host NIC with 192.168.1.4 and the
> vm with 192.168.1.2 .
>
> As Ben says in his blog article, you do not need to use a physical NIC
> at all to communicate between the host and guest. You can use an internal
> virtual network. When you create one of these, it creates an LAC in the OS
> in the parent partition. If you connect the NIC in a vm to this
> network/switch it can communicate with the host through this new LAC.
>
> After you install the Hyper-V role, there is not really much need for the
> parent partition to use the network. Microsoft recommends that you do not
> run any other role in the parent partition. The only need for a network
> connection is for Windows updates or remote administration. Microsoft
> recommends that you have on NIC in the physical machine reserved for this,
> and the setup wizard in R2 prompts you to do this.

> Thanks for the clarification. I didn't catch that it created a virtual
> switch until now.
>
> My goal is to have a dedicated NIC for each child and host and that they
> can all communicate with each other and the network. I'm only using the
> host for remote management and backup purposes. This is how I have it
> setup now.
>
> Physical NIC with static IP 192.168.2.4
> Virtual NIC with only the MVNSP checked (created via Hyper-V manager)
> Physical NIC with cleared checkboxes in the properties sheet
> Within the VM it has a static IP 192.168.2.2
>
> The two physical NICs are attached to a physical switch and I can
> communicate between the child, host and network. Even though this works I
> would like confirmation that this is the correct setup for my needs.
>
> courtk
>
>
>
> "Bill Grant" <not.available@online> wrote in message
> news:(email address - cut out)...
>>
>>
>> "CourtK" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> Hopefully someone can explain this to me. I have two physical NICs on a
>>> server. In Hyper-V Manager I assign one of them to a virtual server.
>>> The NIC I assigned to the virtual server created a Local Area
>>> Connection -3and has Microsoft Virtual Network Switch Protocol checked.
>>> The NIC that was not assigned to the virtual server has a static ip of
>>> 192.168.1.4. Inside the virtual server I assigned 192.168.1.2 but
>>> outside the vitual server it is set to dynamic and picked up
>>> 192.168.1.22. I don't understand the role of the NIC with the dynamic
>>> IP. Should I be assigning a static IP to it and what is it used for?
>>>
>>> From another computer on the same network I tried to ping the host
>>> 192.168.1.4 but couldn't. I could ping 192.16.1.22. I need to make
>>> sure that I can always connect to the host for managing.
>>>
>>> -courtk
>>
>> First up, you do not assign NICs to virtual servers in Hyper-V. You
>> create virtual switches assigned to NICs. You then join the NIC in a vm
>> to the virtual switch.
>>
>> I agree that this is confusing. The best explanation I know of comes
>> from Ben Armstrong's blog.
>>
>> http://blogs.msdn.com/virtual_pc_guy/archive/2008/01/08/understanding-networking-with-hyper-v.aspx
>>
>> This process has been improved in R2, but that is not really much help
>> for you!
>>
>> What do you want your network to do? If you do not want the OS in the
>> parent partition to use this NIC, clear all the check marks from the
>> boxes in the new properties sheet. Leave the MVNSP box ticked it the
>> other properties sheet. This NIC is then dedicated to the virtual switch,
>> and will not have an IP in the parent partition.
>>
>> If both the NICs are plugged into the same physical switch, you should
>> now be able to communicate between the host NIC with 192.168.1.4 and the
>> vm with 192.168.1.2 .
>>
>> As Ben says in his blog article, you do not need to use a physical NIC
>> at all to communicate between the host and guest. You can use an internal
>> virtual network. When you create one of these, it creates an LAC in the
>> OS in the parent partition. If you connect the NIC in a vm to this
>> network/switch it can communicate with the host through this new LAC.
>>
>> After you install the Hyper-V role, there is not really much need for
>> the parent partition to use the network. Microsoft recommends that you do
>> not run any other role in the parent partition. The only need for a
>> network connection is for Windows updates or remote administration.
>> Microsoft recommends that you have on NIC in the physical machine
>> reserved for this, and the setup wizard in R2 prompts you to do this.
>