Charlie,

Could you answer the Dominick's question below? I guess you have not answered it yet so far. I am curious about why sometimes it showed "IP address conflict" during setup, and if it matters about "
Should the manual IP address have matched the virtual IP address on the
Host OS? Or should I have used another address?" which is posted by Dominick.

Thanks,
Patrick




---- from Dominick --------------



I think that did it! Yes, the Host uses DHCP, and the Guest OS had an
APIPA address. So I changed the setting manually to match the virtual
connection the Hyper-V setup created in the Host, and then it appeared
to change its status to having a good network; BUT, it then complained
about an IP address conflict. Was this because it should not match the
virtual connection in the Host's IP address? Or I bet that might have
been because that NIC existing as a normal connection before Hyper-V
grabbed it, so there was a DNS entry for that IP with the Host OS
computer's name?

Anyway - I just manually changed the IP address to one in range that I
knew wasn't taken. And it all works! So clearly the problem has been
that Vista x64 as Guest is getting a DHCP-generated address on my network.

Should the manual IP address have matched the virtual IP address on the
Host OS? Or should I have used another address?

On Thu, 25 Sep 2008 12:37:16 -0700, Patrick wrote:

>Charlie,
>
>Could you answer the Dominick's question below? I guess you have not answered it yet so far. I am curious about why sometimes it showed "IP address conflict" during setup, and if it matters about "
>Should the manual IP address have matched the virtual IP address on the
>Host OS? Or should I have used another address?" which is posted by Dominick.
>
>Thanks,
>Patrick
>

Regardless of the technology, you can't have two machines, physical or
virtual have the same IP address. So no, the IP addresses should not
match, each one needs to be unique.

--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/

True, you can't duplicate the IP address on multiple NICs - virtual or not.
Additionally, unless you are accessing the VM over an external IP/NIC
combination, each physical NIC in the Parent system doesn't necessarily need
an IP assigned to it (a difficult concept at first)...

--
Ryan Sokolowski
MVP - Clustering
MCT, MCITP x3, MCTS x7, MCSE x2, CCNA, CCDA, BCFP


"Steve Jain [MVP]" <noreply.-@-.essjae.com> wrote in message
news:feund4131hhjls3mo96etmjoemhp4ghgt8@xxxxxx

> On Thu, 25 Sep 2008 12:37:16 -0700, Patrick wrote:
>

>>Charlie,
>>
>>Could you answer the Dominick's question below? I guess you have not
>>answered it yet so far. I am curious about why sometimes it showed "IP
>>address conflict" during setup, and if it matters about "
>>Should the manual IP address have matched the virtual IP address on the
>>Host OS? Or should I have used another address?" which is posted by
>>Dominick.
>>
>>Thanks,
>>Patrick
>>

>
> Regardless of the technology, you can't have two machines, physical or
> virtual have the same IP address. So no, the IP addresses should not
> match, each one needs to be unique.
>
> --
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/

As Steve and Ryan have already said, you can't have two IP addresses that
are the same. And you can easily have a physical adapter with no IP address
in Hyper-V. That's normal, even if totally weird.

BTW, I don't see Dominick's question. Sometimes things get out of whack and
we don't see all of the Web posted stuff here on the NNTP side.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Patrick" wrote in message news:2008925153717pwu@xxxxxx

> Charlie,
>
> Could you answer the Dominick's question below? I guess you have not
> answered it yet so far. I am curious about why sometimes it showed "IP
> address conflict" during setup, and if it matters about "
> Should the manual IP address have matched the virtual IP address on the
> Host OS? Or should I have used another address?" which is posted by
> Dominick.
>
> Thanks,
> Patrick
>
>
>
>
> ---- from Dominick --------------
>
> I think that did it! Yes, the Host uses DHCP, and the Guest OS had an
> APIPA address. So I changed the setting manually to match the virtual
> connection the Hyper-V setup created in the Host, and then it appeared
> to change its status to having a good network; BUT, it then complained
> about an IP address conflict. Was this because it should not match the
> virtual connection in the Host's IP address? Or I bet that might have
> been because that NIC existing as a normal connection before Hyper-V
> grabbed it, so there was a DNS entry for that IP with the Host OS
> computer's name?
>
> Anyway - I just manually changed the IP address to one in range that I
> knew wasn't taken. And it all works! So clearly the problem has been
> that Vista x64 as Guest is getting a DHCP-generated address on my network.
>
> Should the manual IP address have matched the virtual IP address on the
> Host OS? Or should I have used another address?