13 replies
by saihib
1. Since this was an upgrade and not a clean install remove and re-install the DNS Server on the DC
2. Enable dynamic updates on DC
3. Make sure you have correct DNS settings on the 2nd server, making sure of the domain name and auotmatic addition to the DNS...Then Promote the second server to DC
by di_cenzo_leo
by darra268
by di_cenzo_leo
by jose_12650
by jose_12650
by di_cenzo_leo
by di_cenzo_leo
by timwalsh
Not knowing the exact process/procedures you used to upgrade the NT4 PDC, I want to review a couple of things:
1. When you installed Win2K on your NT4 PDC, you should have installed Active Directory (AD) in order to create your AD domain. The AD installation routine should have either asked you for the location of a DNS server to host your domain's DNS zone, or prompted you to create one to do so.
1. You should have a local DNS server that hosts a DNS zone of the same name as your AD domain name.
2. If the DNS server is not the same computer as your first Win2K AD Domain Controller (DC), it must point to the DNS server as its Primary DNS server. If the DC is also the DNS server, it must point to itself as Primary DNS.
3. If DNS was set up correctly, you should see 4 folders in the forward lookup zone in addtion to the normal DNS records. These folders are labeled _msdcs, _sites, _tcp, and _udp. These folders hold all the AD-specific DNS records. Without them AD will not work. These records tell all other servers/clients where such AD-specifc objects as the DC are located.
4. Once you installed Win2K on the second server, you must then join that server to the domain before you can install AD to create an additionalDC.
5. You do not need to be operating in native mode in order to add a Win2K DC to the domain. Mixed mode merely implies that NT4 BDCs still exist in the domain.
6. All clients/servers in the domain MUST point to the local DNS server in order for AD to work properly.
The error message you receive (DC can't be found) tells me one of a couple of things isn't correct:
1. DNS wasn't set up properly.
2. The second Win2K server isn't pointed at the DNS server hosting your AD domain.
3. The second Win2K server hasn't been joined to the AD domain.
Hope this helps.
by di_cenzo_leo
by rmarket
by di_cenzo_leo
by di_cenzo_leo
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending