> Hi,
>
> I just got my Dell PowerEdge T300 server (Hyper-V enabled). After
> installing
> Windows 2008 server and adding Hyper-V role, everything was cool. Then I
> installed Vista Ultimate x64 as a virtual machine. The Vista VM has an
> "Unidentified Network" and I could not get it connect to the network.
>
> There are two NIC on the server and I used NIC1 for Windows 2008 server
> host
> and it works fine. I assigned the same NIC (NIC1) to be used as the
> virtual
> network. Is this the cause of the problem? Should I use the other NIC
> (NIC2)
> for virtual machines?
>
> I installed the Integration service to the Vista VM but that seemed not
> solving the issue. I noticed that the Vista VM has an IP adress as
> 169.254.x.x which is out the range in my network (168.192.x.x) but I not
> not
> know wheter I should manually set the IP. The windows 2008 host gets its
> IP
> from DHCP so it is not static.
>
> Thank you so much for your help.

>
>
> "Besh" <(email address - cut out)am> wrote in message
> news:(email address - cut out)...
> > Hi,
> >
> > I just got my Dell PowerEdge T300 server (Hyper-V enabled). After
> > installing
> > Windows 2008 server and adding Hyper-V role, everything was cool. Then I
> > installed Vista Ultimate x64 as a virtual machine. The Vista VM has an
> > "Unidentified Network" and I could not get it connect to the network.
> >
> > There are two NIC on the server and I used NIC1 for Windows 2008 server
> > host
> > and it works fine. I assigned the same NIC (NIC1) to be used as the
> > virtual
> > network. Is this the cause of the problem? Should I use the other NIC
> > (NIC2)
> > for virtual machines?
> >
> > I installed the Integration service to the Vista VM but that seemed not
> > solving the issue. I noticed that the Vista VM has an IP adress as
> > 169.254.x.x which is out the range in my network (168.192.x.x) but I not
> > not
> > know wheter I should manually set the IP. The windows 2008 host gets its
> > IP
> > from DHCP so it is not static.
> >
> > Thank you so much for your help.
>
> You need to create a virtual network linked to on of the physical NICs,
> then link your vm to this virtual network. It doesn't really matter which
> one you use.
>
> If you connect to the server remotely, it is best to dedicate one NIC to
> the host for this purpose and dedicate the other to vms. The NIC used by the
> remotes does not need on IP address on the host.
>
>
>

> Thanks Bill,
>
> I did not create the virtual network first before I added the virtual
> machine. This could be the cause of the issue. I will try to create the
> virtual network first then add the virtual machine see if that fix the
> issue.
>
> "Bill Grant" wrote:
>
>>
>>
>> "Besh" <(email address - cut out)am> wrote in message
>> news:(email address - cut out)...
>> > Hi,
>> >
>> > I just got my Dell PowerEdge T300 server (Hyper-V enabled). After
>> > installing
>> > Windows 2008 server and adding Hyper-V role, everything was cool. Then
>> > I
>> > installed Vista Ultimate x64 as a virtual machine. The Vista VM has an
>> > "Unidentified Network" and I could not get it connect to the network.
>> >
>> > There are two NIC on the server and I used NIC1 for Windows 2008 server
>> > host
>> > and it works fine. I assigned the same NIC (NIC1) to be used as the
>> > virtual
>> > network. Is this the cause of the problem? Should I use the other NIC
>> > (NIC2)
>> > for virtual machines?
>> >
>> > I installed the Integration service to the Vista VM but that seemed not
>> > solving the issue. I noticed that the Vista VM has an IP adress as
>> > 169.254.x.x which is out the range in my network (168.192.x.x) but I
>> > not
>> > not
>> > know wheter I should manually set the IP. The windows 2008 host gets
>> > its
>> > IP
>> > from DHCP so it is not static.
>> >
>> > Thank you so much for your help.
>>
>> You need to create a virtual network linked to on of the physical
>> NICs,
>> then link your vm to this virtual network. It doesn't really matter which
>> one you use.
>>
>> If you connect to the server remotely, it is best to dedicate one NIC
>> to
>> the host for this purpose and dedicate the other to vms. The NIC used by
>> the
>> remotes does not need on IP address on the host.
>>
>>
>>