Not able to ping Azure VMs

Balaji 51 Reputation points

Hi Team,

I have created two VMs in Azure and which are in same region and same vnet.
I am able to ping From Server 1 - to - Server 2
But unable to ping From Server 2 - to - Server 1.

I am getting the error as request timed out.

Can you please assist me on this issue?

(Both VMs are in same VNET and having same inbound and outbound Rules. No changes in network end)

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
5,236 questions
{count} votes

Accepted answer
  1. kongou_ae 171 Reputation points

    Do you use Windows VM? The default configuration of the Windows firewall prohibits ICMP. Could you try to test reachability with Test-NetConnection -Port 3389, please?


    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Dragos Petrisor 1 Reputation point


    I am experiencing same issue. From server A ping works to server B. Viceversa is not. B is a DC so A cannot join the domain either.

    Server B:


    Server A:


    Ping from B to A:


    Ping from A to B:


    I have even disabled firewall completely on B. I re-enabled and defined In and OUT rules for ICMP. Sill does not work.

    @kongouae-0068 ,The connectivity test fails but why is it relevant? That port is RDP and ICMP doesn't go through a specific port.

    Please help me out.

    Best regards,


    0 comments No comments

  2. Sangram Rath 1 Reputation point

    @Balaji-0915 & @DragosPetrisor-3001 there could be many reasons, here's one idea if one of them is in Domain and other is not:

    • There are firewall profiles i.e. Public, Private & Domain, experiment with them by setting the "Enabled = Yes"
    • Check domain remote address, try setting it to "any"
    • Check Public / Private (particularly this) profile
    0 comments No comments

  3. Balaji 51 Reputation points

    Just need to do VNET peering between two networks and allow ICMPV4 protocol for ping in NSG rules

    0 comments No comments

  4. Siva K 1 Reputation point

    Select the affected Virtual Machine.

    Select Networking and then select the network Interface of the VM.

    Screenshot shows the Network interface location.

    Select IP configurations.

    Select the IP.

    If the Private IP assignment is not Static, change it to Static.

    Change the IP address to another IP address that is available in the Subnet.

    The virtual machine will restart to initialize the new NIC to the system.

    Try to RDP to your machine. If successful, you can change the Private IP address back to the original if you would like. Otherwise, you can keep it.

    0 comments No comments