Global Catalog issue??

[Jeff]

Our AD configuration is as follows:

1 domain
2 domain controllers for the domain
each DC is a global catalog server

on the Infrastructure Master I am getting the following event log entry:

Event Type: Error
Event Source: NTDS General
Event Category: Global Catalog
Event ID: 1126
Date: 11/24/2003
Time: 5:28:14 AM
User: Everyone
Computer: AD3
Description:
Unable to establish connection with global catalog.


The server takes a really long time to boot - sits at "Establishing Network
Connection" for an excessive period of time.

Has anyone seens this before? Any ideas?

Thanks,

Jeff

 

[Matjaz Ladava [MVP]]

Is any of your servers multihomed ? Try manually connecting to global
catalog server using ldp.exe on port 3268 (GC port). You could also try to
remove GC from server and later re-add it.

--
Regards

Matjaz Ladava, MCSE, MCSA, MCT, MVP
Microsoft MVP - Active Directory
(e-mail address removed), (e-mail address removed)
http://ladava.com

 

[Jeff]

Is any of your servers multihomed ? Try manually connecting to global
catalog server using ldp.exe on port 3268 (GC port). You could also try to
remove GC from server and later re-add it.

The server in question is multihomed, but we are not using the second NIC.
It is disabled. Does that make a difference?

Also, I was able to connect without a problem to the GC using ldp.exe to
port 3268.

This error seems to appear everytime the server is rebooted. Do you think
the error is a symptom of a greater problem or is it a "false alarm" ???

Thanks,

Jeff

 

[Matjaz Ladava [MVP]]

Check, that your Internal nic is listed first in binding order under
Advanced Settings in Network places.

--
Regards

Matjaz Ladava, MCSE, MCSA, MCT, MVP
Microsoft MVP - Active Directory
(e-mail address removed), (e-mail address removed)
http://ladava.com

 

[Jeff]

I verified that the NIC we are using is listed first in the binding order.
Any other suggestions? I've noticed that a reboot of this domain controller
takes a significant amount of time each time I reboot. Could take up to 20
minutes for it to come back after a reboot.