Hyper-V cannot ping VM from host

Question

I have a small Hyper-V environment, but since today I cannot ping from the VM to outside, and not from the local network to the VM.

My situation/network in short:

Router: 192.168.1.254
My Hyper-V Host/Computer: 192.168.1.10
My Virtual Machine: 192.168.168.1.110
They ALL have gw=192.168.1.254, subnetmask: 255.255.255.0
None of the computers have the windows firewall enabled
The VM is connected via a external Virtual Switch, that is bound to my only NIC in my PC. (Allow management operating system to share this NIC = on)
I always ping using the IP

From my computer (192.168.1.10) I can ping all components in the network, like GW and others. But I cannot ping the VM.

From the VM, I can ping the default gateway, and other VM's, but none of the other NIC's in the network, for example 192.168.1.10

This used to work, I didn't change anything, and it stoped working. I think this has to do with the virtual switch of Hyper-V, anybody have a tip on where to look?

score 13 · Accepted Answer · answered Sep 25 '16 at 08:26

13

Long story short: remove the virtual switch from Hyper-V, recreate it, and everything worked again...

answered Sep 25 '16 at 08:26

Dennis

677
1
9
23

Indeed, solved the issue. – W.M. May 01 '18 at 15:38
Solved for me also. – vukis Sep 14 '18 at 07:16
Still a working solution more than years later on the latest Win 10 Insider build. – paradroid Dec 05 '18 at 01:13
Had the same issue. Everything worked, I didn't change anything. Then it broke. I could ping the VM from another computer, but not from the local machine (the same thing with HTTP access). Very funny, yeah? Recreating the virtual switch solved the problem! – Mike Siomkin Jul 24 '19 at 17:51
Yep good. killed it and made it again. Worked. – Justin Dec 15 '19 at 23:18
Recreation creates a new Ethernet interface. Looks like something went wrong during Hyper-V installation. And, yes, recreation does help. – dibery Oct 14 '21 at 09:21

score 4 · Answer 2 · answered May 02 '19 at 20:20

4

reason is!!Firewall!!

Disable Firewall, or to be specific in the firewall settings, allow bellow app to communicate through fire wall and issue will be resolved:

File and Printer Sharing (ICMS)

answered May 02 '19 at 20:20

Abdullah MF

41
1

in my case the rule was "File and Printer Sharing (SMB-In)" – Okneloper Sep 17 '20 at 08:31

score 1 · Answer 3 · answered Oct 31 '18 at 04:38

Happened to me after host system update. VM client is Windows 7 and must have seen the updated virtual switch as a new network. Recreating virtual switch as above didn't work for me. Solution for me was to either

(1) within VM, set network location from Private to Home

-- or --

(2) within VM, allow network discovery in Private

Hope this helps.

score 0 · Answer 4 · answered Aug 21 '22 at 17:53

When you create a virtual switch, each adapter will show duplicated on the host level, one is the physical itself and the other the virtual version of it.

You probably have a local ip on the physical adapter when it should not even have a TCP protocol.

Set up your local ip on the virtual adapter and check again.

Hyper-V cannot ping VM from host

4 Answers4