VMware Cloud Community
tuczap
Contributor
Contributor
Jump to solution

Nested Hyper-V VM can't ping default gateway

Hi,

In the beginning I must say that I don't consider myself a VMware's product expert.

I've been struggling with my test nested environment for quite a while and finally decided to (hopefully) get some help from pros.

Environment looks like this:

  • Physical VMware ESXi 5.1.0 (promiscuous mode turned on for the vSwitch)
    • Couple of virtual machines, one of them being Hyper-V server (Windows Server 2012 R2) which is configured for nested virtualization - 10.106.5.27
      • On Hyper-V server I have one VM being Windows Server 2012 R2 - 10.106.5.28

Hyper-V server has one NIC and full network connectivity (internal and external: Internet) and in Hyper-V Manager a Virtual Switch is configured in external mode.

VM is connected to this virtual switch via Virtual Network Adapter. It has static IP assigned with subnet mask, default gateway and DNSs same as Hyper-V host. I can ping the host from VM and vice versa both by IP and DNS name. I can't ping other resources from the VM including default gateway and DNS servers ("request timed out"). On VM network status in Network and Sharing Center is:

  • unidentified network
  • Public network
  • access type: no internet access

When I run Troubleshoot Problems tool on VM it says "The default gateway is not available". As I mentioned I can't ping it.

I think that all my connectivity problems are caused by unavailability of default gateway on the VM, but I have no idea of how to solve this issue. When changing the VM's adapter settings from static to DHCP I can't even ping the Hyper-V host.

All of the servers are joined to same domain (VM was migrated from ESXi so it was joined to domain before, but I can't login using domain accounts, probably because of the network problem).

I hope that I described the problem enough but please let me know if you need more information.

0 Kudos
1 Solution

Accepted Solutions
rcporto
Leadership
Leadership
Jump to solution

Try enabling Forged Transmits also on the vSphere vSwitch like you do for Promiscuous Mode.

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto

View solution in original post

0 Kudos
2 Replies
rcporto
Leadership
Leadership
Jump to solution

Try enabling Forged Transmits also on the vSphere vSwitch like you do for Promiscuous Mode.

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
0 Kudos
tuczap
Contributor
Contributor
Jump to solution

Could it be any simpler? I don't know why all resources I've found mentioned only turning on Promiscous Mode and not this option!

Thank you Smiley Happy

0 Kudos