Archived from groups: microsoft.public.win2000.active_directory (More info?)
We currently have a windows 2000 AD domain. Our parent company is
still on a NT 4.0 domain structure. We have a 2 way external trust
between us. They needed control over AD account administration so we
added them to the Account Operator group. Everything is working, but
every time they create a new user the get the following error:
Windows cannot verify that the user name is unique because the
following error occurred while contacting the global catalog: Logon
Failure: unknown user name or bad password
Windows will create the user account, but the use can log on only after
the user name is verified to be unique. Make sure the global catalog
is available.
We have 2 domain controllers and both have a copy of the GC.
Archived from groups: microsoft.public.win2000.active_directory (More info?)
"" wrote:
> We currently have a windows 2000 AD domain. Our parent
> company is
> still on a NT 4.0 domain structure. We have a 2 way external
> trust
> between us. They needed control over AD account
> administration so we
> added them to the Account Operator group. Everything is
> working, but
> every time they create a new user the get the following error:
>
> Windows cannot verify that the user name is unique because the
> following error occurred while contacting the global catalog:
> Logon
> Failure: unknown user name or bad password
>
> Windows will create the user account, but the use can log on
> only after
> the user name is verified to be unique. Make sure the global
> catalog
> is available.
>
> We have 2 domain controllers and both have a copy of the GC.
>
> Any ideas?
may sound like a DNS related problem.
Check the event logs of the DCs and run DCDIAG /V on each to what
might wrong
Archived from groups: microsoft.public.win2000.active_directory (More info?)
All of the DC's on our domain passed (cannot speak for our parent
company's DC's). I'm not sure, but believe that there might be a
problem with the way an account from an externally trusted domain
authenticates to our GC when they create a new user via the MMC. We
created a test account on our domain and tested account creation via
MMC and everything worked fine (no errors). I've also tested doing a
standard delegation (not using the Account Operators - Local group) -
same error. Is there an issue with adding accounts to the Account
Operators group from an externally trusted domain?
The pen is mightier than the sword, and considerably easier to write with.
-- Marty Feldman
"Jake" <TerryWikoff@gmail.com> wrote in message
news:1123249861.143440.67010@g14g2000cwa.googlegroups.com...
> All of the DC's on our domain passed (cannot speak for our parent
> company's DC's). I'm not sure, but believe that there might be a
> problem with the way an account from an externally trusted domain
> authenticates to our GC when they create a new user via the MMC. We
> created a test account on our domain and tested account creation via
> MMC and everything worked fine (no errors). I've also tested doing a
> standard delegation (not using the Account Operators - Local group) -
> same error. Is there an issue with adding accounts to the Account
> Operators group from an externally trusted domain?
>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.