|
Mark,
If
your developers are using ADSI, they can use the "GC:" prefix and serverless
binding in their bind string to connect to a nearby GC.
If
they are using LDAP, they should use DsGetDcName() function from the Platform
SDK and set the bit that indicates they want to locate a
GC.
If
this isn't an option, you can search the CN=Sites, CN=Configuration, DC=...
container for objects of class ntDSDSA and inspect the 0x01 bit of the "options"
attribute. This is set when a DC has been successfully promoted to a
GC.
Checking the isGlobalCatalogReady operational attribute of rootDSE
will only tell you if the DC you've connected to is a global catalog that is
ready to service GC requests; it doesn't help you find a GC to begin with, and
may be set to false when the GC is otherwise busy.
-gil
Gil Kirkpatrick -----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mulnick, Al Sent: Thursday, December 11, 2003 11:14 AM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] finding GCs
|
Title: Message
- [ActiveDir] finding GCs Creamer, Mark
- RE: [ActiveDir] finding GCs Mulnick, Al
- RE: [ActiveDir] finding GCs Tony Murray
- RE: [ActiveDir] finding GCs Gil Kirkpatrick
- RE: [ActiveDir] finding GCs Creamer, Mark
- RE: [ActiveDir] finding GCs Creamer, Mark
- RE: [ActiveDir] finding GCs Mulnick, Al
- RE: [ActiveDir] finding GCs Burns, Clyde
- RE: [ActiveDir] finding GCs Creamer, Mark
- RE: [ActiveDir] finding GCs Creamer, Mark
- RE: [ActiveDir] finding GCs Carlos Magalhaes
