Win2k "secret weapon" domain controller diagnostics

One. Function introduction

Dcdiag.exe is a domain controller diagnostic tool. Before explaining this tool, several concepts must be explained. Domain: Simply put, a network is composed of domains. It is a centralized management unit for data security. It has a unique name. The domain can define security boundaries in the Active Directory. The domain was originally created in Windows NT, and CW2KP is still inherited. 2. Forests (some data is simply called forests): Look at the name to know that this is a collection of many directories. Please refer to the relevant information for the exact meaning.

As we all know, windows2000 has a lot of enhancements to the network function. This diagnostic tool can only be used in the network environment. It is impossible to encounter the domain controller in a single machine environment. Over. Dcdiag can analyze the state of the domain controller in the forest or "organization" and generate a report that aggregates all the problems obtained through the diagnostic test into itself. When the manager or technical support staff analyzes the problem and troubleshoots it, This is a reference for judgment. DcDiag itself can report problems to end users, and in the program, detailed functions and knowledge about how to identify system abnormalities have been encapsulated.

If DcDiag is understood as a framework, then the framework is composed of a series of tests and checks (for the system). Of course, since it is a test, these tests must be performed in a certain order. The program performs the diagnostic test of the domain controller according to the user's choice. From the scope, the test can be for the organizational unit, the site or a single server, or it can be completely tested for all projects. From the execution method, the test can specify either an item or some unnecessary items. Usually the following items should be available:

· Connectivity

· Copy

· Topological Integrity

· Check NC Head Security Description

· Check login rights

· Get domain controller location

· Security boundary

· Check task or role.

· Verification of trust relationships.

There is also a project on trust relationship verification in the previously introduced NetDiag connectivity test tool. (Refer to my previous article "Introduction to Connectivity Test Tools")

II. Using Syntax:

dcdiag /s:DomainController [/n:NamingContext] [/u:DomainUsername /p:{*