MS Windows Active Directory problem

MS Windows Active Directory problem

Anesha,

The most important fact to be kept in mind is that all the domain controllers in one domain are peers of each other. Now all the controllers should be connected to each other with a proper replication topology, which helps the Domain controller locator to find the correct Domain controller, but this can only be possible when the locator have the accurate information so it can locate the proper resource, otherwise, if the domain controller is not properly advertised, the locator is not going to find it.

Each server/ domain controller should be advertising a role in order for the locator to return to that server as candidate.

Nltest tool can be used to properly know about the roles advertised by the server.

Keeping in view the very short explanation above, the issue quoted by you “Domain Controller could not be reached” may be a result of improper topology of different servers and their roles advertised. In my experience this is the most common reason other than the network / connectivity problems, and overloaded server problem.

The network factor can be checked by pinging either by DNS of the server, or by NetBIOS.

The overloaded server can be checked by checking the server’s resources.

You can use Dcdiag tool for all the above checks.

After performing the above you must allocate the proper role to ONE PRIMARY DOMAIN CONTROLLER

Also do perform the following from the client.

On the command prompt write:

 ipconfig /release
 ipconfig /flushdns          Now     Reboot.

 ipconfig /renew

Hope the above resolve the issue

SARA