I connect my child partitions (guests) to the parent partition (host)
through the "default" network, using the "external" connection type. I
suppose it is the way most people will do.

Trying to ping from guest to host (from child to parent) and vice versa
does not work, everything else is fine. I can connect to any other real
computer. If I bridge the 2 lan-interfaces, it works.

Is that the way it is supposed to be?
http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx

-> But, I do have another test-machine, everything works from the
beginning without bridging.

I'm confused.
Thorsten

==
My lab:
Hyper-V RC 0,
WS 2008 and Vista child partitions

If it works on one machine but not on another, I would suspect that the
problem lies with the NIC driver in the host. Do the two machines have the
same type of NIC? If do, do they have the same version of the driver?

"Thorsten Butz" <thbutz@community.nospam> wrote in message
news:%23WQ$nsClIHA.748@TK2MSFTNGP04.phx.gbl...
>I connect my child partitions (guests) to the parent partition (host)
> through the "default" network, using the "external" connection type. I
> suppose it is the way most people will do.
>
> Trying to ping from guest to host (from child to parent) and vice versa
> does not work, everything else is fine. I can connect to any other real
> computer. If I bridge the 2 lan-interfaces, it works.
>
> Is that the way it is supposed to be?
> http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx
>
> -> But, I do have another test-machine, everything works from the
> beginning without bridging.
>
> I'm confused.
> Thorsten
>
> ==
> My lab:
> Hyper-V RC 0,
> WS 2008 and Vista child partitions

So you created a virtual network of type external.
If you have one NIC and were using that to access the root partition, your
machine's network will be reconfigured such that it loses its network
configuration and that you need to reconfigure using a new virtual NIC. The
original NIC has become a virtual switch, networking should go through the
new virtual NIC.

It sounds to me like you did a manual bridging of the virtual switch and
virtual NIC?
You should not need to do that if you properly reconfigured the networking
to the machine.

Matthijs

"Thorsten Butz" wrote:

> I connect my child partitions (guests) to the parent partition (host)
> through the "default" network, using the "external" connection type. I
> suppose it is the way most people will do.
>
> Trying to ping from guest to host (from child to parent) and vice versa
> does not work, everything else is fine. I can connect to any other real
> computer. If I bridge the 2 lan-interfaces, it works.
>
> Is that the way it is supposed to be?
> http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx
>
> -> But, I do have another test-machine, everything works from the
> beginning without bridging.
>
> I'm confused.
> Thorsten
>
> ==
> My lab:
> Hyper-V RC 0,
> WS 2008 and Vista child partitions
>

Hi Matthijs,

you're right: 1 NIC, 1 virtual network = type external.

The original NIC has no more bindings except the "Virtual Network
Switch"; the new synth-NIC has all the config for the parent partition.

That should behave like "Vmware bridged mode". But it did not. My parent
partition could not be reached from the childs. Everything else could
communicate. So, this should be a fault. Glad to know.

Thanks for the response,
Thorsten


02.04.2008 14:19, Matthijs ten Seldam [MSFT]s Mail:
> So you created a virtual network of type external.
> If you have one NIC and were using that to access the root partition, your
> machine's network will be reconfigured such that it loses its network
> configuration and that you need to reconfigure using a new virtual NIC. The
> original NIC has become a virtual switch, networking should go through the
> new virtual NIC.
>
> It sounds to me like you did a manual bridging of the virtual switch and
> virtual NIC?
> You should not need to do that if you properly reconfigured the networking
> to the machine.
>
> Matthijs
>
> "Thorsten Butz" wrote:
>
>> I connect my child partitions (guests) to the parent partition (host)
>> through the "default" network, using the "external" connection type. I
>> suppose it is the way most people will do.
>>
>> Trying to ping from guest to host (from child to parent) and vice versa
>> does not work, everything else is fine. I can connect to any other real
>> computer. If I bridge the 2 lan-interfaces, it works.
>>
>> Is that the way it is supposed to be?
>> http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx
>>
>> -> But, I do have another test-machine, everything works from the
>> beginning without bridging.
>>
>> I'm confused.
>> Thorsten
>>
>> ==
>> My lab:
>> Hyper-V RC 0,
>> WS 2008 and Vista child partitions
>>

Hi Thorsten,

strange behavior then. It has always worked for me, from the early alpha
builds to now.
Did you make a network trace? Did you check firewall issues?
You had networking from the children to anywhere on the external network?
Just not from the children to the parent?
How about the parent to anywhere?

Matthijs


"Thorsten Butz" wrote:

> Hi Matthijs,
>
> you're right: 1 NIC, 1 virtual network = type external.
>
> The original NIC has no more bindings except the "Virtual Network
> Switch"; the new synth-NIC has all the config for the parent partition.
>
> That should behave like "Vmware bridged mode". But it did not. My parent
> partition could not be reached from the childs. Everything else could
> communicate. So, this should be a fault. Glad to know.
>
> Thanks for the response,
> Thorsten
>
>
> 02.04.2008 14:19, Matthijs ten Seldam [MSFT]s Mail:
> > So you created a virtual network of type external.
> > If you have one NIC and were using that to access the root partition, your
> > machine's network will be reconfigured such that it loses its network
> > configuration and that you need to reconfigure using a new virtual NIC. The
> > original NIC has become a virtual switch, networking should go through the
> > new virtual NIC.
> >
> > It sounds to me like you did a manual bridging of the virtual switch and
> > virtual NIC?
> > You should not need to do that if you properly reconfigured the networking
> > to the machine.
> >
> > Matthijs
> >
> > "Thorsten Butz" wrote:
> >
> >> I connect my child partitions (guests) to the parent partition (host)
> >> through the "default" network, using the "external" connection type. I
> >> suppose it is the way most people will do.
> >>
> >> Trying to ping from guest to host (from child to parent) and vice versa
> >> does not work, everything else is fine. I can connect to any other real
> >> computer. If I bridge the 2 lan-interfaces, it works.
> >>
> >> Is that the way it is supposed to be?
> >> http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx
> >>
> >> -> But, I do have another test-machine, everything works from the
> >> beginning without bridging.
> >>
> >> I'm confused.
> >> Thorsten
> >>
> >> ==
> >> My lab:
> >> Hyper-V RC 0,
> >> WS 2008 and Vista child partitions
> >>
>

Thorsten,

I would really like to know what the difference between the two
servers you used is. Do they have the same type of NIC? If so, do they have
the same version of the driver?

There have been a few postings about this sort of problem and I suspect
it might be specific to a particular NIC or NIC driver, because it works for
most people.

"Thorsten Butz" <thbutz@community.nospam> wrote in message
news:%23WQ$nsClIHA.748@TK2MSFTNGP04.phx.gbl...
>I connect my child partitions (guests) to the parent partition (host)
> through the "default" network, using the "external" connection type. I
> suppose it is the way most people will do.
>
> Trying to ping from guest to host (from child to parent) and vice versa
> does not work, everything else is fine. I can connect to any other real
> computer. If I bridge the 2 lan-interfaces, it works.
>
> Is that the way it is supposed to be?
> http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx
>
> -> But, I do have another test-machine, everything works from the
> beginning without bridging.
>
> I'm confused.
> Thorsten
>
> ==
> My lab:
> Hyper-V RC 0,
> WS 2008 and Vista child partitions

I made the tests on a dell-desktop-pc, a vostro, intel-based chipset.
Don't know the exact configuration; it was somewhere in a lab
environment on a customers site. I made a clean-install.

The 2nd pc is a notebook, a core2-duo-based ASUS V2.

I cannot put all the things together again right now. But if I see it
again, I will let you know.

Thorsten

04.04.2008 03:19, Bill Grants Mail:
> Thorsten,
>
> I would really like to know what the difference between the two
> servers you used is. Do they have the same type of NIC? If so, do they
> have the same version of the driver?

Thanks!

"Thorsten Butz" <thbutz@community.nospam> wrote in message
news:%23WnTOJBmIHA.5280@TK2MSFTNGP02.phx.gbl...
>I made the tests on a dell-desktop-pc, a vostro, intel-based chipset.
> Don't know the exact configuration; it was somewhere in a lab
> environment on a customers site. I made a clean-install.
>
> The 2nd pc is a notebook, a core2-duo-based ASUS V2.
>
> I cannot put all the things together again right now. But if I see it
> again, I will let you know.
>
> Thorsten
>
> 04.04.2008 03:19, Bill Grants Mail:
>> Thorsten,
>>
>> I would really like to know what the difference between the two
>> servers you used is. Do they have the same type of NIC? If so, do they
>> have the same version of the driver?

03.04.2008 17:19, Matthijs ten Seldam [MSFT]s Mail:

> Did you make a network trace? Did you check firewall issues?
> You had networking from the children to anywhere on the external network?
> Just not from the children to the parent?
> How about the parent to anywhere?

Of course, I checked it all. Anything worked, firewalls were turned off.
Parent to world, world to parent, child to world, world to child.
Everything was fine, except: parent to child an vice versum.

Thanks indeed for your support, I will post again if I have a DéjÃ-vu.
Thorsten