Low success rate of active name resolution


New install of Azure ATP Sensor on Domain Controller getting warning "Low success rate of active name resolution".


Corp-DC1, failed more than 90% of the time when doing active resolution using NetBIOS, NetworkNameResolverMethodRdpTlsName, RPC over NTLM and reverse DNS. It might affect detections capabilities and increase amount of FPs.


Check that the sensor can reach the DNS server and that Reverse Lookup Zones are enabled.
Check that Port 137 is open for inbound communication from MDI sensors, on all computers in the environment.
Check that Port 135 is open for inbound communication from MDI sensors, on all computers in the environment.
Check all network configuration (firewalls), as these could prevent communication to the relevant ports.


Need assistance interpreting or getting more information about this error. Domain controller is Server 2019 serving several sites/subnets. All other services work fine, we see no error messages in DNS Server or DNS client.


10 Replies
best response confirmed by RNalivaika (Contributor)

Did you make sure the ports are open as described in


If yes, open a support case, so  they can increase the trace level on your workspace to tell you more about when it fails.

@Eli Ofek you mean Office365 support ?

I will try that, thank you!

@Eli Ofek Can you confirm the frequency with which the sensor runs this "name resolution" process?

For every connection opened to the DC, if there wasn't a connection from this endpoint already in the past 30 sec.
This is current implementation and might change without notice, so do not rely on  it in any way.

@Eli Ofek Can we the timeout settings for the name resolution( set to 500 ms), if we put up a request with the support team for our tenant? Also, please confirm if 500 ms timeout is the existing configuration from Microsoft side?

Yes, currently the default is still 500ms. can change without notice.

We have the technical means to change it, but only if investigation shows this is needed and there is no other way. Why do you want to change it  and to what number ?


@Eli Ofek MS Support provided me with a sample list of IP adresses failing NNR and we were able to make the necessary changes on the network, so this helped.