Forum Discussion
Low success rate of active name resolution using RPC over NTLM
Microsoftthatguy000 , You can ignore this warn message you found on the logs. it's unrelated.
AS for the name resolution issue, it's a bit tricky to resolve it on your own, I strongly suggest to open a support ticket and get guidance from the support engineer about which data you need to collect and how.
Eli
Well that's disappointing.. one would think if a service is deemed "Ready for the public" then it would have documentation and tools available to the enduser to resolve these issues. So much for logic.
Thank you for the quick response tho.
- EliOfek
thatguy000 , This is indeed the aspiration, sadly, when the service depends on a sensor that still has to run on prem, there are environmental challenges which we cannot easily control (Yet we always try to improve that in new ways).
The issue you mentioned is not happening due to misconfiguration of the product or service, but due to on prem network characteristics and configuration (Giving that you followed the deployment guide already, and made sure requested ports are properly open). Those at times can be complicated to troubleshoot for some customers.While we are currently researching the development of tools that will make it easier for the customers to troubleshoot this issue, currently getting guidance from support is still the quickest way for most customers.
