General discussion

Locked

Win2k Migration

By di_cenzo_leo ·
I'm migratiing to Win2k from an NT 4.0 domain. I have successfully upgraded the primary DC to Win 2k. I have three BDC's that still need migrating. I'm still obviously running in mixed mode. My problem is that I'm trying to add a Win2k server as a bdc for the domain. It has a clean install of Win2k and is a dual xenon rig. But so far when I try to activate active directory I get an error message stating that a domain controller for the domain can't be found. DNS and Wins are running on the PDC.Do I have to migrate my other servers first and switch to native mode or is this possible? Any suggestions would be greatly appreciated.

This conversation is currently closed to new comments.

13 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Win2k Migration

by saihib In reply to Win2k Migration

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

Collapse -

Win2k Migration

by di_cenzo_leo In reply to Win2k Migration

Poster rated this answer

Collapse -

Win2k Migration

by darra268 In reply to Win2k Migration

Have you run DCPromo on the newly upgraded win2k DC?

Collapse -

Win2k Migration

by di_cenzo_leo In reply to Win2k Migration

Poster rated this answer

Collapse -

Win2k Migration

by jose_12650 In reply to Win2k Migration

If you were activating/adding your second DC from the DHCP console of the first domain controller, you are likely to fail. Run DCPROMO on the second W2k Server and configure it as a member server of the domain. This will not be a BDC as domain controllers in W2K environment are operating on equal footing.

Collapse -

Win2k Migration

by jose_12650 In reply to Win2k Migration

What I mean is to run DCPROMO on the second server and configfure it as a domain controller of an existing domain.

Collapse -

Win2k Migration

by di_cenzo_leo In reply to Win2k Migration

Poster rated this answer

Collapse -

Win2k Migration

by di_cenzo_leo In reply to Win2k Migration

Ok let me clarify a little. Yes I'm on the computer that I want to make a bdc. I have wins and dns enabled. We use static ips here so no dhcp, and servers should have their own ip. The machine authenticates to the network, but when I start the AD wizard to add it as additional domain controller for an existing domain. at the end of the wiazard it tells me "Failed finding a suitable domain controller for the domain." "The specified domain either does not exist or could be contacted"

Collapse -

Win2k Migration

by timwalsh In reply to Win2k Migration

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.

Collapse -

Win2k Migration

by di_cenzo_leo In reply to Win2k Migration

Poster rated this answer

Back to Windows Forum
13 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums