How to identify Hyper-V guest IP addresses

The host should not need an IP address.

I am assuming you have created a new virtual switch, assigned the second NIC to it and then also a virtual nic in the guest.

You say you cannot ping outside the network? What can you ping ON the network, if you can ping the router or another physical host on th public network IP range, then hyperV networking is operating correctly..

Your issue (as I suspect if the above is true) is relating to the default gateway of the guest, the router which the guest should send all traffic to if it is not destined for the local network.

Have you set the default gateway in the guests network adapter properties to the router on the public network?

Also, does this guest have access to the internal network too? As it could be the case that you end up with two default gateways (one from the internal network virtual adaptor and one from the public virtual network adaptor).

If this is the case you will need to make a decision on which route your default traffic should take and remove one of the default routes.

If you still need certain traffic to exit via the 'other' adaptor, you can always ensure certain IP's/Network ranges are reached by a certain network by adding static routes as so:

Say we have the following: Guest with two virtual adaptors, one on the public network, one on the private; Public IP: 192.168.1.11 Public Subnet Mask 255.255.255.0 (/24) Public Gateway/Router 192.168.1.1

Internal IP: 192.168.2.11 Internal Subnet Mask 255.255.255.0 (/24) Internal Gateway/Router 192.168.22.1

If you have removed the default gateway IP from the internal network adaptor, all traffic bound for networks OTHER than locally connected networks (192.168.1.0/24 and 192.168.2.0/24) will go via the public gateway at 192.168.1.1 (as it's the only default gateway now configured on the guest)...

However, what if 192.168.100.0/24 was only available via the internal network's router? You can add the following rule to tell the guest to route this particular range of IP addresses via the internal network:

route add 192.168.100.0 mask 255.255.255.0 192.168.22.1

//TrX

It sounds like your virtual switch may be misconfigured. Check out this article and verify your settings. If your host can't ping the VM, then you have some kind of switching/routing problem.