I had an issue with my hyper-v virtuals all not being able to ping the 2008
host.
Not sure how long it was like this, but I found out when I tried to grab a
file off the 2008 box and couldn't.

it had me stumped, because I work on the 2008 box, and all the virtuals it
hosts - remotely - from my desktop, I could ping each and every one of them.

but there was no network communication between the virtuals and the 2008 box
they sat on.

my first thought was that I must have done something to the network config
of hyper-v - I hadn't.

It turned out that I had disabled the network in 2008 somehow.
now this was new to me, I haven't used 2008 much, nor am I a vista guy.

in XP or 2003 I had but one network connection and it was either on or it
wasn't
in 2008 with hyper-v - defining a network in hyper-v - even if it's just
connecting externally through the hosts nic - creates a new network
connection in 2008.

to get to this, start-control panel- network and sharing center then click
'manage network connections' I had one there that was disabled - I think that
happend via some pop up in response to something else I had done earlier that
day.

Hope this s save someone some time!

Hyper-V creates a virtual switch for an existing NIC, so you end up with two
NICs - the original one, that no longer has an IP address, and the new
virtual switch. Disabling either of them is not going to give you a good
result.

It's also important to understand there are three different kinds of
connections for the virtual networks: external, that allows connections to
the outside world, internal, that allows connections between VMs on that
switch, and to the parent partition (host), but not past the host, and
private, which ONLY allows connections between VMs on that switch. (No
connections to the host or the outside world.)

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


"jack" <jack@discussions.microsoft.com> wrote in message
news:ECFDA8DD-11F4-4E81-9736-95D1E4DF93A6@microsoft.com...
>I had an issue with my hyper-v virtuals all not being able to ping the 2008
> host.
> Not sure how long it was like this, but I found out when I tried to grab a
> file off the 2008 box and couldn't.
>
> it had me stumped, because I work on the 2008 box, and all the virtuals it
> hosts - remotely - from my desktop, I could ping each and every one of
> them.
>
> but there was no network communication between the virtuals and the 2008
> box
> they sat on.
>
> my first thought was that I must have done something to the network config
> of hyper-v - I hadn't.
>
> It turned out that I had disabled the network in 2008 somehow.
> now this was new to me, I haven't used 2008 much, nor am I a vista guy.
>
> in XP or 2003 I had but one network connection and it was either on or it
> wasn't
> in 2008 with hyper-v - defining a network in hyper-v - even if it's just
> connecting externally through the hosts nic - creates a new network
> connection in 2008.
>
> to get to this, start-control panel- network and sharing center then click
> 'manage network connections' I had one there that was disabled - I think
> that
> happend via some pop up in response to something else I had done earlier
> that
> day.
>
> Hope this s save someone some time!

as a follow up - I thought I had it licked, and I tried it agian and still
no luck - not sure if a reboot would have ed - I know I rebooted one of
the virtuals and still no luck.

Charlie - I was using the external connection type before (it was working
till I messed it up!)

so what I did was
- stop each virtual machine.
- using the hyperv manager - removed the external network definition
when I did this, my extra connection dissapeared from windows.
also all my virtuals network configs went to an error state.
- I set each virtual config to no no network
- I recreated an external network I named it 'bound to nic - external'
- i went into settings for each virtual and set the network to use 'bound
to nic - external'

There was again an extra network connection in windows
booted a virtual and was able to ping the host. Whew! I would not have
wanted to rebuild that machine!

so a little bit tedious but I managed to get things back in acton!

"Charlie Russel - MVP" wrote:

> Hyper-V creates a virtual switch for an existing NIC, so you end up with two
> NICs - the original one, that no longer has an IP address, and the new
> virtual switch. Disabling either of them is not going to give you a good
> result.
>
> It's also important to understand there are three different kinds of
> connections for the virtual networks: external, that allows connections to
> the outside world, internal, that allows connections between VMs on that
> switch, and to the parent partition (host), but not past the host, and
> private, which ONLY allows connections between VMs on that switch. (No
> connections to the host or the outside world.)
>
> --
> Charlie.
> http://msmvps.com/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
>
> "jack" <jack@discussions.microsoft.com> wrote in message
> news:ECFDA8DD-11F4-4E81-9736-95D1E4DF93A6@microsoft.com...
> >I had an issue with my hyper-v virtuals all not being able to ping the 2008
> > host.
> > Not sure how long it was like this, but I found out when I tried to grab a
> > file off the 2008 box and couldn't.
> >
> > it had me stumped, because I work on the 2008 box, and all the virtuals it
> > hosts - remotely - from my desktop, I could ping each and every one of
> > them.
> >
> > but there was no network communication between the virtuals and the 2008
> > box
> > they sat on.
> >
> > my first thought was that I must have done something to the network config
> > of hyper-v - I hadn't.
> >
> > It turned out that I had disabled the network in 2008 somehow.
> > now this was new to me, I haven't used 2008 much, nor am I a vista guy.
> >
> > in XP or 2003 I had but one network connection and it was either on or it
> > wasn't
> > in 2008 with hyper-v - defining a network in hyper-v - even if it's just
> > connecting externally through the hosts nic - creates a new network
> > connection in 2008.
> >
> > to get to this, start-control panel- network and sharing center then click
> > 'manage network connections' I had one there that was disabled - I think
> > that
> > happend via some pop up in response to something else I had done earlier
> > that
> > day.
> >
> > Hope this s save someone some time!
>

Honestly, I haven't had any issues at all with the networking - other than
the lack of drivers for the new synthetic NICs until you get the Integration
Components installed.

I really like the new "internal" connection type - it's a great fit for a
lot of the testing I use virtualization for - gives me access to the parent
partition where I can store various utilities and resources, while still
isolating me from the rest of my network.

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


"jack" <jack@discussions.microsoft.com> wrote in message
news:E769EC73-12CA-4A08-A32A-6A16A9BF53A4@microsoft.com...
> as a follow up - I thought I had it licked, and I tried it agian and
> still
> no luck - not sure if a reboot would have ed - I know I rebooted one
> of
> the virtuals and still no luck.
>
> Charlie - I was using the external connection type before (it was working
> till I messed it up!)
>
> so what I did was
> - stop each virtual machine.
> - using the hyperv manager - removed the external network definition
> when I did this, my extra connection dissapeared from windows.
> also all my virtuals network configs went to an error state.
> - I set each virtual config to no no network
> - I recreated an external network I named it 'bound to nic - external'
> - i went into settings for each virtual and set the network to use 'bound
> to nic - external'
>
> There was again an extra network connection in windows
> booted a virtual and was able to ping the host. Whew! I would not have
> wanted to rebuild that machine!
>
> so a little bit tedious but I managed to get things back in acton!
>
> "Charlie Russel - MVP" wrote:
>
>> Hyper-V creates a virtual switch for an existing NIC, so you end up with
>> two
>> NICs - the original one, that no longer has an IP address, and the new
>> virtual switch. Disabling either of them is not going to give you a good
>> result.
>>
>> It's also important to understand there are three different kinds of
>> connections for the virtual networks: external, that allows connections
>> to
>> the outside world, internal, that allows connections between VMs on that
>> switch, and to the parent partition (host), but not past the host, and
>> private, which ONLY allows connections between VMs on that switch. (No
>> connections to the host or the outside world.)
>>
>> --
>> Charlie.
>> http://msmvps.com/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>>
>> "jack" <jack@discussions.microsoft.com> wrote in message
>> news:ECFDA8DD-11F4-4E81-9736-95D1E4DF93A6@microsoft.com...
>> >I had an issue with my hyper-v virtuals all not being able to ping the
>> >2008
>> > host.
>> > Not sure how long it was like this, but I found out when I tried to
>> > grab a
>> > file off the 2008 box and couldn't.
>> >
>> > it had me stumped, because I work on the 2008 box, and all the virtuals
>> > it
>> > hosts - remotely - from my desktop, I could ping each and every one of
>> > them.
>> >
>> > but there was no network communication between the virtuals and the
>> > 2008
>> > box
>> > they sat on.
>> >
>> > my first thought was that I must have done something to the network
>> > config
>> > of hyper-v - I hadn't.
>> >
>> > It turned out that I had disabled the network in 2008 somehow.
>> > now this was new to me, I haven't used 2008 much, nor am I a vista guy.
>> >
>> > in XP or 2003 I had but one network connection and it was either on or
>> > it
>> > wasn't
>> > in 2008 with hyper-v - defining a network in hyper-v - even if it's
>> > just
>> > connecting externally through the hosts nic - creates a new network
>> > connection in 2008.
>> >
>> > to get to this, start-control panel- network and sharing center then
>> > click
>> > 'manage network connections' I had one there that was disabled - I
>> > think
>> > that
>> > happend via some pop up in response to something else I had done
>> > earlier
>> > that
>> > day.
>> >
>> > Hope this s save someone some time!
>>

> I had an issue with my hyper-v virtuals all not being able to ping the 2008
> host.
> Not sure how long it was like this, but I found out when I tried to grab a
> file off the 2008 box and couldn't.
>
> it had me stumped, because I work on the 2008 box, and all the virtuals it
> hosts - remotely - from my desktop, I could ping each and every one of them.
>
> but there was no network communication between the virtuals and the 2008 box
> they sat on.
>
> my first thought was that I must have done something to the network config
> of hyper-v - I hadn't.
>
> It turned out that I had disabled the network in 2008 somehow.
> now this was new to me, I haven't used 2008 much, nor am I a vista guy.
>
> in XP or 2003 I had but one network connection and it was either on or it
> wasn't
> in 2008 with hyper-v - defining a network in hyper-v - even if it's just
> connecting externally through the hosts nic - creates a new network
> connection in 2008.
>
> to get to this, start-control panel- network and sharing center then click
> 'manage network connections' I had one there that was disabled - I think that
> happend via some pop up in response to something else I had done earlier that
> day.
>
> Hope this s save someone some time!

I have WS 2008 enterprise x64. I am running 32bit Server 2003 std on an local hyper-v session. The hyper-v session can get to the outside world (external network settings in hyper-v manager), along with internal servers (file print, shares, etc). I am assuming that i should be able to see this witout setting the network to Internal yes? However, I can't ping or get to the parent 2008 server via IP or Name. I am trying to configure usb-over-network and they can't see eachother. I have done a few things people have commented on to fix this, but no success please .

Thanks,
David

Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com

> I have WS 2008 enterprise x64. I am running 32bit Server 2003 std on an
> local hyper-v session. The hyper-v session can get to the outside world
> (external network settings in hyper-v manager), along with internal
> servers (file print, shares, etc). I am assuming that i should be able to
> see this witout setting the network to Internal yes? However, I can't
> ping or get to the parent 2008 server via IP or Name. I am trying to
> configure usb-over-network and they can't see eachother. I have done a
> few things people have commented on to fix this, but no success please
> .
>
> Thanks,
> David
>
> Posted via http://www.VirtualServerFaq.com - Brought to you by Business
> Information Technology Shop - http://www.bitshop.com

Networking is pretty much the same whether you are using physical or
virtual machines or networks. The networking protocols are still the same.
They cannot tell the difference.

First check that the machines are in the same network. Is the NIC in the
vm connected to the external network (ie the one linked to the physical NIC
in the host)?

Next do an ipconfig /all on both the host and guest and check that they
are in the same IP subnet. Check that TCP/IP is actually working in the
guest by pinging its own IP address.

If the guest can ping itself but not the host, check if the host can
ping the guest. If it works that way but not guest to host, enable ICMP echo
in the firewall settings of the host.