Discussion Locked

Error: conn. with Global Catalog

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

i have a Windows 2000 SP4 domain controller which has ISA & DNS installed and running on the same machine...

Today when i opened the AD users and computers it has failed to connect to the domain, it displayed a red cross on the AD snap-in..
When i checked the event viewer for errors, i found the following:

Error: Event ID 1126, Unable to establish a connection with global catalog.

i can display the domain in the AD users and computers by right clicking and Connect to domain controller,
No when i close the ADusers and computers and re-open it the same problem again...

and there is no group policy displayed at any level and cant add or do anything with it...

now if i promote another member server to DC and make it the GC, does it fix the problem?

also i have another DNS server running with Active directory integrated zone on another machine if this might help...

any suggestions to get this problem fixed...

cheers,

6 replies

by saihib

See M838400 for a hotfix applicable to Microsoft Windows 2000.

See M842208 and the link to "EventID 1126 from source Active Directory" for more details on this problem.

Woodrow Wayne Collins (Last update 11/8/2004):
Make sure a global catalog is available in the forest, and is reachable from this domain controller. You may use the Nltest utility to diagnose this problem.

Carl Kepford (Last update 9/21/2004):
After applying MS security bulletin MS04-011 on a DC that is a catalog server, that domain controller after reboot does not register itself as a Global Catalog server in DNS. Hence, other domain controllers that are not global catalog servers may get this error. A hotfix is available from Microsoft see M841395.

by omarhib

thanks for the reply,
Even the AD sites and services is not running... i cant even connect to the domain from there...

by dumphrey

Looks like Saihib has covered this ground well. Also can try ipconfig /registerdns from the command line on the DC, as well as nltest /dsregdns and netdiag /fix. These 3 should force the DC to register any and all records with DNS. But it looks more like global catalog is missing to me. I would try to fix GC on the server you have, if that doesnt work in a reasonable amount of time, then add a second DC, and it should become a GC if it cant find one in the local site.

by dumphrey

Are you on the DC when trying to connect to AD sites and services, or on a remote machine with admin tools installed? If remote, log on to the server itself and try. If you cant get in at all, I would set up the second DC and then see if that fixes the ptoblem.

by omarhib

Ok, i have istalled another domain controller on the network and did the replication.... but none of the client computers were able to logon to the domain until i rejoin it to the domain...
Now is that normal that i have to go to every workstation (approx. 300 client computer) and rejoin'em to the domain...

This discussion is closed to new replies.