Cannot ping between a Unix VM and a Windows VM in same subnet

Jones, Brian H 0 Reputation points

I am working on a LAB and I am just trying to establish ping my Unix VM which is running Ubuntu 20.04 and my Windows VM which is running Windows 11. While I am running EVE-NG on my Unix VM, both VMs have a public IP assigned and part of the same subnet that is assign to a single VM. Windows and Unix both have firewall disabled. If I reboot them a copy of times, it works about 20-30% of the time.

From a packet capture from the UNIX VM I see the following:

04:44:05.005882 IP > ICMP echo request, id 1, seq 164, length 40

04:44:05.010636 IP > ICMP udp port 32995 unreachable, length 136

So I see the packet coming into the interface and the interface is set correctly as it gets DHCP and from my home PC, it works.

04:44:02.362624 IP > ICMP echo request, id 2, seq 54225, length 40

04:44:02.362670 IP > ICMP echo reply, id 2, seq 54225, length 40

So it is not working on the private side between the VMs.

Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
1,825 questions
{count} votes

1 answer

Sort by: Most helpful
  1. KapilAnanth-MSFT 27,916 Reputation points Microsoft Employee

    @Jones, Brian H

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    I understand that you are not able to ping between your Linux VM and Windows VM in the same subnet.

    I take it that the

    • Private IP of Linux VM is
    • And Private IP of Windows VM is

    From the packet capture, (Windows VM to Linux VM)

    • We can see the packets are being received by the Linux VM
    • This indicates that the platform routing is correct
    • However, the Linux VM is not even responding to the ICMP Ping requests.
    • This indicates there is some misconfiguration/issue in the OS of the Linux VM
    • In case the Linux VM has responded with a ICMP Ping reply and the Windows VM has not seen it, we can suspect there is a routing issue or packet drop at the platform.
    • Also, since you stated the issue is no longer reproducible once you had rebooted the system, further indicates this has something to do with the OS (OS level firewall/IP tables)

    Should the issue resurface again, I would suggest you to may file a support ticket, where a support engineer can have a specialized 1:1 screen share session to pinpoint the issue.

    Kindly let us know if this helps or you need further assistance on this issue.



    Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

    0 comments No comments