Global Catalog cannot be located? 2

[thetango]

Well I guess things were going to smoothly.
Upgraded an old NT4 domain controller to Server2003.
Added the new hardware that is running Server2003 to the domain.
Removed AD from the old upgraded server and removed it.

Now whenever I try to add or chance a user I get "Global catalog cannot be located".

The orginal BDC (still running NT4) is still in the domain until I do some research on moving NTGateway off of it. Running NTGateway on the old BDC for limited assess to some files on a remote Netware location.

Any ideas?

Thanks

 

[NFI]

So have you actually got Active Directory installed on any of your servers?

 

[thetango]

Yes, AD is running on the new domain controllers. But when I run "dcdiag" everything passes but at the end of the list there is:

Starting test: FsmoCheck
Warning: DcGetDcName<CC_SERVER_REQUIRED> call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.

The users, PCs, ect. show up in active directory.

How do I "start" the Global Catalog?

 

[rolo1968]

Open Active Directory Sites and Services.
Sites->Site-Name->Servers->(server name)
Right click on NTDS settings and check the box next to Global Catalog.

 

[thetango]

THANKS - Found it - Seems to be working now.

Well time to do a bit of research on Trusts & Wins with a NT4 remote domain and NTGATEWAY.

Thanks again