Event ID 1126 Source NTDS General
| Event ID | 1126 |
| Source | NTDS General |
| Type | Error |
| Description | Unable to Establish Connection with the Global Catalog |
| English, please! | Request a translation of the event description in plain English. |
| Concepts to understand |
What is the role of the Global Catalog? What is NTDS and what are the roles of its components? |
| Comments |
Anonymous
(Last update 2/9/2009): I had this problem on one of two DC in a site. In sites and services I unchecked the "This server is Global Catalog" checkbox for both servers in this site. After a while I checked it for the server which had this error again and the error was gone. Mihai Andrei (Last update 12/19/2006): This problem occurs if the Net Logon service on the domain controller does not start before the World Wide Web Publishing Service starts. See M929100 for details on this situation. This event can occur when promoting a domain controller to a global catalog server. See M910204 for additional information about this issue. Peter Hayden (Last update 11/13/2005): In one case, this event occurred on a domain controller when the DNS Server Windows component was uninstalled. In another case, this event appeared when an attempt to transfer a FSMO role (the PDC role) by running NTDSUTIL on another domain controller failed. Ensure that the primary network adapter is configured with the IP address of at least one available DNS Server. If using DSN Active Directory integrated zones then resolve any problems with Active Directory replication. Ionut Marin (Last update 4/1/2005): 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. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! 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. Andy Haer (Last update 11/28/2003): I had this problem trying to promote a replicated AD machine to be the "first" DC after my original DC went bye-bye. After switching all the roles and getting the active database to rebuild, I was left with this error. Here is the fix I used: 1. Go to Administrative Tools, Sites and Services. 2. Browse the tree, Sites -> Default first name -> Servers -> your DC -> NTDS settings. 3. Right click NTDS settings and choose properties. 4. Check the box Global Catalog. 5. Reboot. Anne Jan Elsinga (Last update 11/28/2003): I got this kind of errors after I changed the DC with a new one, namely after I promoted the new DC, demoted the old DC (which remained a GC). To fix the problem I modified the Service Location Record (SRV) for _gc in DNS that it would point to the new DC. TmWeah (Last update 11/28/2003): This error will also appear if you have removed the Global Catalog tick in NTDS Settings located under "AD Sites and Services". Rick Smith Check your domain Controllers Local Policy User Rights Assignment to be sure that Exchange Enterprise Servers account is under Manage Auditing and security Log. If not add it or run Domain Prep from the Exchange 2000 CD again to fix all security issues. Then re-install Exchange service pack. Shawn Westerhoff This can be caused by clocks on AD controllers being out of sync. Adrian Grigorof As the error says, verify the availability of the server hosting the Global Catalog (network, DNS, etc..) and if the Global Catalog is online. See M256287 for more information. Sometimes, certain applications may affect the functionality of the Global Catalog (Citrix, Surf Control, and others). As per M318170, this problem may occur if you have a damaged object. M313167 points to a connectivity problem between Exchange 2000 and the Global Catalog. As per Microsoft, this behavior can occur if you lock the system partition and remove the Everyone group from various locations. See M305837 for more details and how to fix this. If the error occurs on a Small Business Server, see M322267. Alex Curvers This event can also occur when the Netlogon service fails. David Gatewood Ensure that the Netlogon service is running. This service must be running for the GC to "Advertise". Eliminate any errors that cause the Netlogon server to fail to start. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! |
| Links | M256287, M305837, M313167, M318170, M322267, M838400, M841395, M842208, M910204, M929100, How to use the Nltest Domain-User tool, EventID 1126 from source Active Directory |
| Search | Google Web - Microsoft Support - Bing - EventID.Net Queue - More links... |
| Feedback | Send comments - Notify me when updated |
| Print version |