I'm in the process of setting up my 1st VM solution as part of our new
network build. The server that I'm using to carry out my testing has dual
Ethernet ports, one assigned to the DC (Host) and the other assigned to the
guest VM.

I've gone into HyperV and assigned the spare Ethernet port to my VM, which
then creates the virtual port which has a fixed IP assigned to it. I then
also have to assign an IP to the VM, is this right or am I doing something
wrong? Seems that I'm using two IP addresses for no particular reason?

Thanks in advance, AStaley.

if an either card)port is strictly for vm use not for host use, you only
need the virtual network protocol on and nothing else. Hence no need for two
IP address per card

"Andrew Staley" <not@newsgroup> wrote in message
news:E1FD8A66-9C38-4B8D-84F0-E2669BB023F4@newsgroup

> I'm in the process of setting up my 1st VM solution as part of our new
> network build. The server that I'm using to carry out my testing has dual
> Ethernet ports, one assigned to the DC (Host) and the other assigned to

the

> guest VM.
>
> I've gone into HyperV and assigned the spare Ethernet port to my VM, which
> then creates the virtual port which has a fixed IP assigned to it. I then
> also have to assign an IP to the VM, is this right or am I doing something
> wrong? Seems that I'm using two IP addresses for no particular reason?
>
> Thanks in advance, AStaley.
>

"Andrew Staley" <not@newsgroup> wrote in message
news:E1FD8A66-9C38-4B8D-84F0-E2669BB023F4@newsgroup

> I'm in the process of setting up my 1st VM solution as part of our new
> network build. The server that I'm using to carry out my testing has dual
> Ethernet ports, one assigned to the DC (Host) and the other assigned to
> the guest VM.
>
> I've gone into HyperV and assigned the spare Ethernet port to my VM, which
> then creates the virtual port which has a fixed IP assigned to it. I then
> also have to assign an IP to the VM, is this right or am I doing something
> wrong? Seems that I'm using two IP addresses for no particular reason?
>
> Thanks in advance, AStaley.

If this is your first attempt, you are not off to a good start. Running AD
in the parent partition is not something I would do. The recommendation is
to run the Hyper-V role ONLY on the machine you use to host your vms.

The NIC that is used by the vms does not require a IP address on the
host/parent partition. Each vm has its own NIC with its own MAC address and
its own IP.

Read this extract from Ben's blog to understand what happens when you
create a virtual switch/network.

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

Thank you for the replies. I now have the network cards working as
expected.

Why is it a bad idea to have AD running on your host machine, is this to do
with taking resources away from the guests as well as losing some of the
benefit's of using a virtual environment such as switching guest to a 2nd
server?

Andrew.

"Andrew Staley" <not@newsgroup> wrote in message
news:E1FD8A66-9C38-4B8D-84F0-E2669BB023F4@newsgroup

> I'm in the process of setting up my 1st VM solution as part of our new
> network build. The server that I'm using to carry out my testing has dual
> Ethernet ports, one assigned to the DC (Host) and the other assigned to
> the guest VM.
>
> I've gone into HyperV and assigned the spare Ethernet port to my VM, which
> then creates the virtual port which has a fixed IP assigned to it. I then
> also have to assign an IP to the VM, is this right or am I doing something
> wrong? Seems that I'm using two IP addresses for no particular reason?
>
> Thanks in advance, AStaley.
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4370 (20090826) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4374 (20090827) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

Basically, yes. You can run other roles on lightly loaded test rigs, but
for a production server the recommendation is to run the Hyper-V role only
in the parent partition.


"Andrew Staley" <no@newsgroup> wrote in message
news:8132CEBF-50AA-483E-9903-EA5BCF589625@newsgroup

> Thank you for the replies. I now have the network cards working as
> expected.
>
> Why is it a bad idea to have AD running on your host machine, is this to
> do with taking resources away from the guests as well as losing some of
> the benefit's of using a virtual environment such as switching guest to a
> 2nd server?
>
> Andrew.
>
> "Andrew Staley" <not@newsgroup> wrote in message
> news:E1FD8A66-9C38-4B8D-84F0-E2669BB023F4@newsgroup

>> I'm in the process of setting up my 1st VM solution as part of our new
>> network build. The server that I'm using to carry out my testing has
>> dual Ethernet ports, one assigned to the DC (Host) and the other assigned
>> to the guest VM.
>>
>> I've gone into HyperV and assigned the spare Ethernet port to my VM,
>> which then creates the virtual port which has a fixed IP assigned to it.
>> I then also have to assign an IP to the VM, is this right or am I doing
>> something wrong? Seems that I'm using two IP addresses for no particular
>> reason?
>>
>> Thanks in advance, AStaley.
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus
>> signature database 4370 (20090826) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>

>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4374 (20090827) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>