Cause: Identity Management server with Active Directory integration support configured replies differently from to NetLogon queries compared to Active Directory.
Consequence: Unlike Active Directory at least the following differences in behavior are present:
* No response to NetLogon query when querying over TCP based LDAP
* Does not response when DnsDomain is not present in query.
* Does not return a LDAP_RES_SEARCH_RESULT to sender when query does not match, just hangs.
These differences may cause errors in tools sending the NetLogon queries.
Fix: Fix the NetLogon query responder.
Result: The above mentioned issues in NetLogon replies are no longer present.