Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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. 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 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?
share|improve this question

Just write in the IP-Adress without the port. ADExplore won't crash and list the Active Directory.

Alternative you can use the JXplorer. There you can add a specific port.

share|improve this answer
If i simply connect to the server without specifing the port i only get the catalog for the domain the server is responsible for, but i don't see any entries for the other domains that are listed in the global catalog of that server. – Oliver Aug 10 '11 at 10:00

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.