NNR in a UNIX environment

%3CLINGO-SUB%20id%3D%22lingo-sub-2218288%22%20slang%3D%22en-US%22%3ENNR%20in%20a%20UNIX%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2218288%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20we%E2%80%99re%20having%20a%20DC%20which%20is%20getting%20isolated%20via%20its%20own%20AD%20subnet%20as%20it%20only%20serves%20our%20backup%20procedure%20rather%20than%20providing%20any%20other%20service%20to%20the%20domain.%20Because%20of%20the%20nature%20of%20the%20AD%2C%20there%20is%20still%20an%20A%20record%20for%20the%20domain%20pointing%20to%20this%20server%20and%20some%20non%20Windows%20devices%20getting%20to%20it%20via%20round%20robin.%20These%20are%20mainly%20UNIX%20devices%2C%20because%20they%20don%E2%80%99t%20support%20the%20AD%20site%20concept.%20When%20looking%20at%20the%20NNR%20options%2C%20I%20do%20believe%20that%20the%20only%20supported%20option%20in%20an%20enterprise%20environment%20is%20DNS.%20This%20DC%20is%20constantly%20getting%20flagged%20that%20it%20is%20not%20able%20to%20resolve%2090%25%20of%20the%20hosts%2C%20as%20it%20can%20%E2%80%9Conly%E2%80%9D%20resolve%20via%20DNS.%20Is%20there%20a%20way%20of%20handling%20this%20problem%20better%20or%20am%20I%20wrong%20with%20my%20interpretation%20of%20this%20health%20alert%3F%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2219569%22%20slang%3D%22en-US%22%3ERe%3A%20NNR%20in%20a%20UNIX%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2219569%22%20slang%3D%22en-US%22%3EWhich%20methods%20are%20mentioned%20in%20the%20alert%20as%20failing%20more%20than%2090%25%20of%20the%20time%3F%3CBR%20%2F%3EAlso%2C%20you%20mention%20the%20device%20is%20isolated%2C%20but%20it%20appears%20it%20accepts%20connections%20from%20outside%20or%20else%20the%20sensor%20would%20not%20try%20to%20NNR%20them...%20it%20only%20happens%20as%20a%20response%20to%20incoming%20connection.%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi, we’re having a DC which is getting isolated via its own AD subnet as it only serves our backup procedure rather than providing any other service to the domain. Because of the nature of the AD, there is still an A record for the domain pointing to this server and some non Windows devices getting to it via round robin. These are mainly UNIX devices, because they don’t support the AD site concept. When looking at the NNR options, I do believe that the only supported option in an enterprise environment is DNS. This DC is constantly getting flagged that it is not able to resolve 90% of the hosts, as it can “only” resolve via DNS. Is there a way of handling this problem better or am I wrong with my interpretation of this health alert?

Thanks

4 Replies
Which methods are mentioned in the alert as failing more than 90% of the time?
Also, you mention the device is isolated, but it appears it accepts connections from outside or else the sensor would not try to NNR them... it only happens as a response to incoming connection.
The message I am getting is “x sensor/s failed more than 90% of the time when doing active resolution using NetBIOS, RDP over TLS, RPC over NTLM and reverse DNS. It might affect detection capabilities and increase amount of FPs”. We have 10 AD sites configured of which 9 have subnets with clients assigned to them. 1 site contains only the DCs IP as a subnet. That’s the isolation I am referring to. As mentioned, the A record for the domain is still assigned to the IP of this server, hence the UNIX devices are finding it. Reverse DNS is working, but none of the other 3 options as they are Windows proprietary or require to be on the same subnet as the DC.
That's a problem...
in theory you can disable some of the methods, but it will be for the entire workspace, so it won't be a good idea.
We are working to find better ways to do NNR with non windows machines, but not something I can share an ETA about.
Thanks for your response
www.000webhost.com