Upgrade from NT4 Terminal Servers to W2K Servers 1

[JH24]

I did an upgrade of a NT4 Domain at the weekend to W2K, the problems that i am having are as follows.

The PDC upgraded to the DC and has Active Directory installed on it with the correct Users/User Groups that were in the NT4 domain.
However i cant get the old BDC to become a DC with Active directory on it...the error i get is that it cant find a DC for that domain.

Also i cant open Active Directory from the MMC on a Memeber W2K Server.
Users can login fine and trust relationships also work fine with other domains.

Any ideas what i am doing wrong?? Am thinking it must be a DNS issue but if i do a TRACERT from the old BDC it can resolve the DC and visa versa.

Thanks
James

 

[ashleym]

Are you running the new Win2k AD domain in mixed mode? If so, point the BDC's DNS to the new Win2k PDC and it should see the domain no problem and upgrade.

AM

 

[GlenJohnson]

Am thinking it must be a DNS issue but if i do a TRACERT from the old BDC it can resolve the DC and visa versa.

Anything in your event logs?

Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

http://www.johnsoncomputers.us

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

"Once the game is over, the king and the pawn return to the same box."

 

[JH24]

It is running in a mixed mode domain at the moment.
I have the old BDC upgraded to W2K now but it is when i am trying to get it to a W2K DC that the problems are occuring.
If i do a Tracert from either machine it resolves correctly. If i do a IPCONIFIG /ALL i can see that they both have the same DNS Suffix. I have the old BDC pointing to the W2K PD that is running the DNS on it and i have the W2K PD pointing to itself for DNS.

 

[dholbrook]

Since you have the old BC updated to a WIn2000 Server, remember that upgrading an NT box to WIn2000 does not give you the same machine as a clean build of Win2000, and the upgraded system can do some wierd things as a result of garbage left behind, funny permissions, etc. Always better to do a clean build once the Domain has been transferred, if at all possible.

Have you had any problems adding any other systems to the domain?

You might try taking the old bdc out of the domain to a workgroup, rebooting and then moving it back into the domain, reboot, then trying the dcpromo. This sometines clears out old domain garbage, especially in systems that were BDC in the old domain. Still recommend a clean rebuild if at all possible though.

HTH
David