I am unable to ping my Loadbalancer's public IP Address

Question

I am unable to ping my Loadbalancer's public IP Address

KEERTHANA S 0

Hi there, I am unable to ping my Loadbalancer's public IP Address. I have configured the Health Probes and Load Balancing Rules. On running diagnostics, it says that the firewall in my 2 VMs are blocking the inbound http traffic.. Can you please let me know how to disable them? and How do I proceed? Thanks

Prrudram-MSFT 28,491 Reputation points Microsoft Employee Moderator

2023-04-10T18:53:37.8633333+00:00
Hello KEERTHANA S,

Firewall, or a network security group could be blocking the port on the load balancer backend pool VMs. If the firewall on the VM is blocking the probe port, or one or more network security groups configured on the subnet or on the VM, is not allowing the probe to reach the port, the VM is unable to respond to the health probe. Validation and resolution

If the firewall is enabled, check if it is configured to allow the probe port. If not, configure the firewall to allow traffic on the probe port, and test again.

From the list of network security groups, check if the incoming or outgoing traffic on the probe port has interference.

Also, check if a Deny All network security groups rule on the NIC of the VM or the subnet that has a higher priority than the default rule that allows LB probes & traffic (network security groups must allow Load Balancer IP of 168.63.129.16).

If any of these rules are blocking the probe traffic, remove and reconfigure the rules to allow the probe traffic.

Test if the VM has now started responding to the health probes.

Tag me in your comments if the above helps!
Prrudram-MSFT 28,491 Reputation points Microsoft Employee Moderator

2023-04-19T18:08:28.4333333+00:00

@KEERTHANA S

Any update here?

Your answer

Prrudram-MSFT 28,491 Reputation points Microsoft Employee Moderator

2023-04-10T18:53:37.8633333+00:00

Hello KEERTHANA S,

Firewall, or a network security group could be blocking the port on the load balancer backend pool VMs. If the firewall on the VM is blocking the probe port, or one or more network security groups configured on the subnet or on the VM, is not allowing the probe to reach the port, the VM is unable to respond to the health probe. Validation and resolution

If the firewall is enabled, check if it is configured to allow the probe port. If not, configure the firewall to allow traffic on the probe port, and test again.

From the list of network security groups, check if the incoming or outgoing traffic on the probe port has interference.

Also, check if a Deny All network security groups rule on the NIC of the VM or the subnet that has a higher priority than the default rule that allows LB probes & traffic (network security groups must allow Load Balancer IP of 168.63.129.16).

If any of these rules are blocking the probe traffic, remove and reconfigure the rules to allow the probe traffic.

Test if the VM has now started responding to the health probes.

Tag me in your comments if the above helps!
Prrudram-MSFT 28,491 Reputation points Microsoft Employee Moderator

2023-04-19T18:08:28.4333333+00:00

@KEERTHANA S

Any update here?

Share via

I am unable to ping my Loadbalancer's public IP Address

Your answer