Check the firewalls. By default ICMPv4 would be blocked.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a Hyper-V host with 2 Private Virtual Switches named as Production and Management. Now I have 2 VM's listed as below.
VM1: NIC1-Management(192.168.100.10)
VM1: NIC2-Production(192.168.101.10)
VM2: NIC1-Management(192.168.100.11)
VM2: NIC2-Production(192.168.101.11)
Now I am able to ping 192.168.100.11 from 192.168.100.10 and vice versa but unable to ping 192.168.101.11 from 192.168.101.10 and vice versa.
How can I achieve this?
Check the firewalls. By default ICMPv4 would be blocked.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
Sorry for the delay go stuck in other works.
Firewall is disabled in all profiles in all servers.
The interface used to send out packets is determined by the local routing table. You can look at the computer's routing table by opening up a command prompt and typing ROUTE PRINT
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
Hello there,
In Hyper-V, we always don't recommend to bridge the Virtual Switch adapter with physical network adapters in the host. The correct way to implement networking in Hyper-V for VM communication and internet is to create an external Virtual Switch.
You can look into this thread for the detailed discussion of this topic and the reason the communication might not happen https://learn.microsoft.com/en-us/answers/questions/204807/hostsguests-cannot-access-each-other-ping-destinat.html
-----------------------------------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept it as an answer--