How to connect AD Explorer from Sysinternals to Global Catalog

Posted by Oliver on Server Fault See other posts from Server Fault or by Oliver
Published on 2011-05-12T08:11:22Z Indexed on 2012/09/11 9:41 UTC
Read the original article Hit count: 245

I'm using the sysinternals AD Explorer quite frequently to search and inspect an Active Directory without any big problems.

But now i'd like to connect not only to a single AD Server. Instead i like to inspect the global catalog.

If i enter within the AD Explorer connect dialog only the dns name of the machine (e.g. dns.to.domain.controller) 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'm going to add the default port number (3268) for the global catalog in the form dns.to.domain.controller:3268 AD Explorer will simply crash without any further message.

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.

  • So any hints or tips to access the global catalog out of AD Explorer?
  • Or there are any other nice tools like AD Explorer out there that doesn't have any problems to access the global catalog?

© Server Fault or respective owner

Related posts about active-directory

Related posts about sysinternals