Created a rule allowing connection over port 389 to an azure vm, all of azures tools such as verify IP connection do not find a problem, but any attempt to test the connection fails.
Created a rule allowing connection over port 389 to an azure vm, all of azures tools such as verify IP connection do not find a problem, but any attempt to test the connection fails.
Hi JosephMiller,
If IP verify confirms that there is no problem, then the NSG configuration is correct. If the connectivity fails, log in to the destination VM and check if LDAP ports are locally accessible. Also check if the Windows Firewall is not blocking incoming connections.
Regards,
Msrini
16 people are following this question.
Needed inbound rules within NSG for Windows VM with Azure DevOps Agent
Trending on MSDN: Unable to change Subnet or add new NIC of new Subnet in new Resource Group
Azure Site Recovery - networking design
Windows update on VM's stopped working after blocking outgoing connections to internet
Load Balancer GetVirtualMachineScaleSet looking for non-existent VM