Additional Domain Controller

I have seen somthing similar that had to do with the reverse lookup zone not being in place or configured properly for the new server. More info would help such as are yo using dcpromo? When exactly do you get the error? Is DNS using dynamic updates?

First, W2K does not use PDC's and BDC's like NT4 did. Any W2K Domain Controller (DC) can be'demoted' to a stand alone or member server, and any stand alone or member server can be promoted to a DC.

A DC in W2K is really a 'replica Domain Controller'.

I'd try building this server as a stand alone/memeber server, and then once you've got it in the domain, go ahead and promote it using DCPROMO.EXE

Let me know if this helps.

-Bill

try adding the PDCs IP address to the new DCs primary DNS address. Then try to join the network.

Dear All,

Thank You for your response, I have checked up my DNS and all the parameters set were correct . All the query statements for DNS as per Microsoft DNS trouble shooter were succesful, Even then I could not elevate my Server to join the Active Directory.

I tried the following option and it worked:

Using Dcpromo, I created a new domain successfully and after reboot I demoted the server. After this I tried to join my present active directory and it worked . I do not know where I went wrong but this procedure worked and there were no errors.

Thanks Again
Dilip

Step-by-Step Guide to Setting up Additional Domain Controllers.

http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/domaincntrl.asp

(REMOVE SPACES from the pasted URL.)

MAxwell

This question was auto closed due to inactivity