Vista - child OS local only connectivity, can only ping itself

Hi,

I set this up a while ago and didn't have this problem, so I am sure this is
something really silly I am overlooking and hoping it is an easy for someone
to crack.

I have a server 2008 core with only the hyper-v role enabled. It has two
NICs (dual port broadcom). I used Hyper-V Manager to remote manger the
Hyper-V host. I used Virtual Network Manager to create an External network
called "Hyper-V switch" and bound it to the second NIC. The aforementioned
physical NIC's IP settings are:
IP: 10.124.6.254/22
Gateway: 10.124.4.254

I then created my first virtual machine and added a virtual NIC assigned to
the "Hyper-V switch" network I created earlier.

I found that after the child OS (Small Biz Srvr 2008) had been installed I
could not get it to connect to anything. First I saw that it couldn't
resolve the DNS forwarder addresses. I checked my Watchguard firewall
policies and that's not it - no traffic is being logged. The child OS's IP
settings are as follows:
IP:10.124.6.1/22
Gateway: 10.124.4.254
I tried to ping the host and it fails with "reply 10.124.6.1: destination
host unreachable". I found this in a technet article about this reply: "If
the message is "Reply From < IP address >: Destination Host Unreachable,"
then the routing problem occurred at a remote router, whose address is
indicated by the "< IP address >" field. Use the appropriate utility or
facility to check the IP routing table of the router assigned the IP address
of < IP address >."

The thing is that the IP in the reply is the IP of the child OS's NIC, so
what can that mean? To be sure it is not the Windows Firewall I disabled
this using netsh, both on the client OS and the host. Still no luck. It
can also not ping the Watchgaurd gateway address 10.124.4.254 from the
child. The host OS can ping the Watchgaurd gateway no problem, but if it
pings the child it returns "reply 10.124.6.254: destination host
unreachable".

Integration services has been installed. The RTM version of Hyper-V
(6.0.6001.18016) is installed.

Please help.

TIA,

Jarryd

"Jarryd" <jarryd@newsgroup> wrote in message
news:0FFD6C42-4398-4A28-92C5-FCE30A97E714@newsgroupWhen you create a virtual switch you completely change the configuration
of the NIC as far as the parent partition is concerned. See this entry in
Ben's blog.

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

Hi Bill,

To be honest I think that this was just one of those silly occasions where
the best thing to do is delete and start again. What I did differently was
this:
1.) configured the first NIC of the broadcom dualport card as the one to be
used as the virtual switch, and
2.) the second one for management.
3.) I have a both these plugged into two separate ports on my watchgaurd
firewall, let's not get into why, but for that reason I didn't configure the
management NIC with a gateway address.
4.) I then removed (rather that simply reconfiguring) the virtual network
using the Hyper-v Manager and recreating it using the first NIC (see point
one above).
5.) I then reconfigured the child's virtual NIC to use the new network,
and...
VIOLA!

Maybe none of the changes made a difference and just needed a fresh start,
who knows. Shall we just not worry about it? Haha.

Jarryd


"Bill Grant" <not.available@newsgroup> wrote in message
news:ekVpsXhRKHA.4020@newsgroup