"FB" <FB@newsgroup> wrote in message
news:6415475C-3D71-4428-B11C-3B04DB6754DB@newsgroup

>
> Host and Guest can´t communicate.
>
> I´ve installed an Win2008 SP2 Standard 64 + Hyper-V (Host) in a DELL
> PowerEdge 2950-III. One NIC (Broadcom II)
>
> I´ve installed the Windows 2003 R2 SP2 Standard 64 (inside Hyper-V, Guest)
> and changed the Network Adapter from Legacy to standard after the firts
> boot
> of the Win2003 Server.
>
> I´m sure i can share the Physical NIC of the DELL Server, so the same
> Physical adapter can be used by the Host and the Guest, right? Or am i
> wrong?
>
> I noticed that the Physical NIC of the DELL Server (Local Area Connection)
> have only one component selected (Virtual Switch or something similar) and
> after created the Virtual Switch (Extenal mode) a new card appears on the
> DELL, behaving like a new NIC, but su´pporting the Virtual NIC, without
> specified IP address.
>
> The Virtual Swicth is "external", connected to the Broadcomm NIC and the
> Host and the Gues can´t communicate each other.
>
> Why?
>

Microsoft recommends that you have one NIC of the host not linked to a
virtual network. This is particularly important if you plan to remotely
administer the server.
I would recommend having at least two NICs in your Hyper-V server.


See this article for an explanation of what happens when you create an
external virtual network.

http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx

You can for testing, but for production, I'd go with the
recommendation of having more than 1.

--
Bob Comer


On Fri, 17 Jul 2009 04:07:01 -0700, FB <FB@newsgroup>
wrote:

>
>If i understood: No, i can´t have only one NIC with Hyper-V...
>
>
>"Bill Grant" wrote:
>

>>
>>
>> "FB" <FB@newsgroup> wrote in message
>> news:6415475C-3D71-4428-B11C-3B04DB6754DB@newsgroup

>> >
>> > Host and Guest can´t communicate.
>> >
>> > I´ve installed an Win2008 SP2 Standard 64 + Hyper-V (Host) in a DELL
>> > PowerEdge 2950-III. One NIC (Broadcom II)
>> >
>> > I´ve installed the Windows 2003 R2 SP2 Standard 64 (inside Hyper-V, Guest)
>> > and changed the Network Adapter from Legacy to standard after the firts
>> > boot
>> > of the Win2003 Server.
>> >
>> > I´m sure i can share the Physical NIC of the DELL Server, so the same
>> > Physical adapter can be used by the Host and the Guest, right? Or am i
>> > wrong?
>> >
>> > I noticed that the Physical NIC of the DELL Server (Local Area Connection)
>> > have only one component selected (Virtual Switch or something similar) and
>> > after created the Virtual Switch (Extenal mode) a new card appears on the
>> > DELL, behaving like a new NIC, but su´pporting the Virtual NIC, without
>> > specified IP address.
>> >
>> > The Virtual Swicth is "external", connected to the Broadcomm NIC and the
>> > Host and the Gues can´t communicate each other.
>> >
>> > Why?
>> >

>>
>> Microsoft recommends that you have one NIC of the host not linked to a
>> virtual network. This is particularly important if you plan to remotely
>> administer the server.
>> I would recommend having at least two NICs in your Hyper-V server.
>>
>>
>> See this article for an explanation of what happens when you create an
>> external virtual network.
>>
>> http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx
>>
>>
>>
>>