Discussion Locked

Can't See First W2K Domain Controller

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

I'm hoping someone can please help me with this. I have set up two W2K domain controllers, both with Active Directory, inside one domain. When I first set everything up about six months ago, everything worked fine. Both servers could see other, and so could the workstations, etc. But, within the last two weeks, the workstations suddenly starting having long logon periods, or not being able to log on at all. Now within the last week, the second domain controller suddenly can't see thefirst domain controller anymore in My Network Places. I can do a computer search for the first server and find it, and I can ping it. But, it doesn't appear in My Network Places.

The initial problem is that I keep getting the Event ID:1000 and 1001, and I'm missing Group Policies folders. I tried to perform the Microsoft Knowledge Base solutions, but I run into the error that it can't find the other domain controller when it's time to re-install the Domain Controller Group Policy object. So, I wanted to re-install Active Directory on the second DC to re-sync it with the first DC. When I try to un-install Active Directory, it gives me a message saying that it can't find the first DC. I think I may have a DNS problem, but I don't know enough about DNS to know which records to look for and/or to add. I think my big mistake, initially, was installing Active Directory on both of the boxes while they were stand-alone servers, instead of connecting them with a hub or switch and then installing Active Directory. Any thoughts or ideas? Also,I thought that in Windows 2K, both servers were more of less equal in terms of policies and Active Directory settings,etc. Why does it need to see the other server before it will allow me to uninstall Active Directory?

5 replies

by timwalsh

While all DCs in an AD domain are considered co-equals for most services, the first DC in a forest/domain has some additional roles assigned to it. These roles are known as Flexible Single Master Operations (FSMO) roles. There are a total of 5 (3 that exist in every AD domain, and 2 that exist only at the root of the forest) and any role can exist on only one DC in a given domain (or forest). By default these roles are assigned to the first DC installed in a forest or domain.

The root of your problem partially relates to the fact that your DCs were not connected when you installed AD. You essentially have 2 different domains. In order to setup a contiguous domain, all DCs must be able to "see" each other at the time of installation.

AD also needs access to a DNS server that accepts dynamic updates in order to install correctly. If you are trying to use your ISPs DNS, chances are that is causing the remainder of the problem.

If you are hosting your own DNS, and AD was setup correctly, in your DNS forward lookup zone you will see folders labled _msdcs, _sites, _tcp, and _udp. Each folder can have subfolders and multiple records. The chances of you being able to manually enter all the correct records are not very good. Without the correct records, AD will not work correctly.

Although you probably don't want to hear this, my suggestion would be to start from scratch and set up AD correctly. You might be able to re-install AD on the second DC (if the first one appears to be working correctly and has the necessary DNS records), but it sounds like you will need to wipe the drive and reinstall the OS if you can't get AD to uninstall.

Good luck.

by cg it

To add to Tim's answer [which pretty much covers the problem] there is a AD connector [Exchange 2000 uses this for access to AD] which you can install on the BDC to allow AD access running on the PDC and for replication. [this negates having to install AD on both servers [which as Tim pointed out, was probably the inital cause of your problem].

This discussion is closed to new replies.