IgnoreGCFailures

[Guest]

Hi all

I have windows 2000 Adv server, SP4 deployed on four nodes for 2x
active/passive cluster solution.

I am using the 'domainlet' approach for this purpose and have followed the
necessary steps and all is working fine by taking out the global catalog role
and putting the registry key "IgnoreGCFailures".

My questions is:
I keep getting error "1126 - NTDS general - unable to establish connection
with global catalog" in the event log of the 'original' global catalog server
I used to setup active directory.

How can I stop this error being reported in the event log?

Thanks in advance
Bryan wiggins

 

[Ryan Hanisco]

Bryan,

This is an error with the Infrastructure Master doing its maintenance. It
can mean there was a problem transferring roles or locating the master. I
would take a look at the DNS configuration for the GCs and make sure that
there isn't anything odd there.

You can also use NLTEST to get a better idea of what is wrong.

Finally, you could move or transfer (don't seize) the role off of the
cluster and try to move it back -- or just run it elsewhere.

 

[Guest]

Hi Ryan

Thanks for getting back to me.

I transfered the 'Infrastructure Master Role' from the first installed DC
(which is not a GC) to another DC within the domain (should this really
matter when no server is acting as a GC?)

1: The error occurred again on the hour from the last event logged

2: I had another error - 1534

"this machine holds the Domain Master Role, and is not a GC. These two
states are incompatible. Either this machine should be made a GC or the role
should be transferred to a machine that is a GC".

DNS is fine as all nodes can connect to the GC when I make the first DC a GC
without a problem.

I know it would be easier for me to just deploy a GC as it is only four
nodes and I doubt replication traffic would make a dent in this setup but I
really want to make the 'domainlet' approach work by not requiring a GC if at
all possible.

Any further help very much appreciated.

Best rgds and thanks
Bryan Wiggins

 

[ptwilliams]

In a single-domain forest, or indeed a multi-domain forest where all DCs are
GCs, the IM is redundant.

This error is nothing to worry about unless you have multiple domains and
non-GC DCs.

-- http://www.msresource.net/content/view/14/46/


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net


Hi Ryan

Thanks for getting back to me.

I transfered the 'Infrastructure Master Role' from the first installed DC
(which is not a GC) to another DC within the domain (should this really
matter when no server is acting as a GC?)

1: The error occurred again on the hour from the last event logged

2: I had another error - 1534

"this machine holds the Domain Master Role, and is not a GC. These two
states are incompatible. Either this machine should be made a GC or the role
should be transferred to a machine that is a GC".

DNS is fine as all nodes can connect to the GC when I make the first DC a GC
without a problem.

I know it would be easier for me to just deploy a GC as it is only four
nodes and I doubt replication traffic would make a dent in this setup but I
really want to make the 'domainlet' approach work by not requiring a GC if
at
all possible.

Any further help very much appreciated.

Best rgds and thanks
Bryan Wiggins

 

[Guest]

Hi Paul

Cheers for the info.

I would like to have my Active Directory run with no GC's for my cluster
servers deployment as in the 'domainlet' scenario.

I would like to stop the error being logged on the initial node I used to
setup AD - It is not reported on any of the 3 other nodes which are DC's.
- Do you know of a way that I can do this?

Thanks
Bryan

 

[ptwilliams]

It's showing up because the IM and GC reside on that box. You can either
ignore it, or move one of the two roles elsewhere.

I'd ignore it, but that's just me. I recommend you run all DCs as GCs.


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net


Hi Paul

Cheers for the info.

I would like to have my Active Directory run with no GC's for my cluster
servers deployment as in the 'domainlet' scenario.

I would like to stop the error being logged on the initial node I used to
setup AD - It is not reported on any of the 3 other nodes which are DC's.
- Do you know of a way that I can do this?

Thanks
Bryan

 

[Guest]

Hi Paul

I had moved the IM role to another DC last week but was still getting the
same error. I made all DC's > GC's yesterday.

Thanks for your input and your article was a good read I must say.

Rgds
Bryan

 

[ptwilliams]

Hey, thanks very much!!

It needs updating...I'll get round to it one day. Glad it helped ;-)


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net


Hi Paul

I had moved the IM role to another DC last week but was still getting the
same error. I made all DC's > GC's yesterday.

Thanks for your input and your article was a good read I must say.

Rgds
Bryan