Lesson 8: Troubleshooting Active Directory
This lesson describes some problems you may encounter that relate to Active Directory and possible solutions.
After this lesson, you will be able to Troubleshoot Active Directory
Estimated lesson time: 10 minutes
Troubleshooting Active Directory
Table 11.11 describes Active Directory troubleshooting scenarios.
Table 11.11 Active Directory Troubleshooting Scenarios
| Symptom: Cannot add or remove a domain | |
|---|---|
| Cause | Solution |
The domain naming master is not available. This may be caused by a network connectivity problem. It may also be due to a failure of the computer holding the domain naming master role. |
Resolve the network connectivity problem. Or, repair or replace the domain naming master computer. It may be necessary to seize the domain naming master role. |
| Symptom: Cannot create objects in Active Directory | |
| Cause | Solution |
The relative ID master is not available. This may be caused by a network connectivity problem. It may also be due to a failure of the computer holding the relative ID master role. |
Resolve the network connectivity problem. Or, repair or replace the computer holding the relative ID master role. It may be necessary to seize the relative ID master role. |
| Symptom: Cannot modify the schema | |
| Cause | Solution |
The schema master is not available. This may be caused by a network connectivity problem. It may also be due to a failure of the computer holding the schema master role. |
Resolve the network connectivity problem. Or, repair or replace the computer holding the schema master role. It may be necessary to seize the schema master role. |
| Symptom: Changes to group memberships are not taking effect | |
| Cause | Solution |
The infrastructure master is not available. This may be caused by a network connectivity problem. It may also be due to a failure of the computer holding the primary domain controller emulator role. |
Resolve the network connectivity problem. Or, repair or replace the computer holding the primary domain controller emulator role. It may be necessary to seize the primary domain controller emulator role. |
| Symptom: Clients without Active Directory client software installed cannot log on | |
| Cause | Solution |
The primary domain controller emulator is not available. This may be caused by a network connectivity problem. It may also be due to a failure of the computer holding the primary domain controller emulator role. |
Resolve the network connectivity problem. Or, repair or replace the computer holding the primary domain controller emulator role. It may be necessary to seize the primary domain controller emulator role. |
| Symptom: Clients are unable to access resources in another domain | |
| Cause | Solution |
There has been a failure of the trust between the domains. |
Reset and verify the trust between the domains. The PDC emulator must be available for a trust to be successfully reset. |
In this lesson you examined some problems you may encounter with Active Directory and possible solutions.