The global catalog itself works as expected under the given name and port number, cause our apache server use exactly this address and port number to authenticate some users. If i'm going to add the default port number (3268) for the global catalog in the form dns.to.ntroller:3268 AD Explorer will simply crash without any further message. dns.to.ntroller) that is serving the global catalog i only receive the concrete domain for which it is responsible, but not the whole forest (that's normal behaviour and expected by me).

If i enter within the AD Explorer connect dialog only the dns name of the machine (e.g. Second check your sp level in your servers as well as the version of the mmc make sure is 3. It may help you while learning how to write LDAP queries. Open perf monitor and check for rogue programs running in the background. Lookup a user or computer and view converted schema attributes that are normally not readable.

Instead i like to inspect the global catalog. Microsoft Sysinternals - Active Directory Explorer If you are starting to write your first queries this tool may help you to explore your AD structure and the required syntax of queries. Completely free utility for Active Directory. I'm using the sysinternals AD Explorer quite frequently to search and inspect an Active Directory without any big problems.īut now i'd like to connect not only to a single AD Server. AD Explorer, provided by Microsoft as part of the Sysinternals suite, which can be used to interactively browse an Active Directory, as well as generate a.

Sysinternals active directory explorer