by "Joe Kaplan" <joseph.e.kaplan@[EMAIL PROTECTED]
>
Aug 8, 2008 at 06:33 PM
Ok, that's interesting. It sounds like some kind of funky behavior with DC
locator. As to whether this is an actual problem or expected behavior is
hard to say. Sometimes you have something messed up with DNS.
Your workaround sounds totally reasonable, assuming that a GC in the
domain
of the current machine is what you want to use.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
<arnon97@[EMAIL PROTECTED]
> wrote in message
news:573502c5-8bac-4c5c-acb6-d34e36de8769@[EMAIL PROTECTED]
> Thanks for the suggestions.
>
> I poked around on the MSDN site and it alluded to the fact that these
> GC binds might want to include a server or domain, in the form of,
> GC://server/OU=... or GC://domain/OU=...
>
> When I included the name of the domain I have joined (retrieved from
> NetGetJoinInformation), the 'scoped' GC binds returned as quick as
> expected.
>
> Arnon
