Unable to establish connection with global catalog

  • Thread starter Thread starter Antonin Koudelka
  • Start date Start date
A

Antonin Koudelka

I tried to upgrade my development server form 2000 to 2003. When upgrading
the computer started rebooting in a loop. I re-installed 2000 and restored
everything from backup. It seems to be working.

However, I have in the Directory Services event log an eventID 1126,
"Unable to establish connection with global catalog.", source NTDS general,
every hour and every half an hour in the System Log an eventID 16650, source
SAM, "The account-identifier allocator failed to initialize properly. The
record data contains the NT error code that caused the failure. Windows 2000
will retry the initialization until it succeeds; until that time, account
creation will be denied on this Domain Controller. Pleas look for other SAM
event logs that may indicate the exact reason for the failure."

How can I fix this?

Antonin
 
Concerning the SAM 16650 errors, you can attempt to seize the RID
master to itself (I know its sounds funky) and then see if the errors
reappear, or there's

a possibility that the DC logging these did not finish its initial
sync of SYSVOL (run a "net share" and you should see SYSVOL/Netlogon
being shared). If you

do not, I would run a D2 (non-auth restore) on the SYSVOL replica set:

840674 How to force a non-authoritative restore of the data in the
Sysvol
http://support.microsoft.com/?id=840674

If this is the only DC in the domain, you can run a D4 (auth restore)
of SYSVOL (I wouldnt recommend running a D4 if there are multiple DCs
in the domain

unless you ABSOLUTELY know what you're doing!):

315457 How to rebuild the SYSVOL tree and its content in a domain
http://support.microsoft.com/?id=315457

On the 1126 error, if you enabled a DC as a GC but didnt reboot it,
the Exchange box will choke:

321318 The top Exchange 2000 directory service support issues
http://support.microsoft.com/?id=321318


Chris Malone
Microsoft Directory Services
 
Back
Top