活动目录：添加新的DC时遇到麻烦

我有一个3 DC的域名。一个开始失败，所以我提出了一个新的。所有运行的Win 2003。

问题：4台机器之间似乎存在复制问题，但我无法弄清楚是什么原因造成的。所有在DNS上的注册都和我能做到的一样。

我怎么知道有问题？ Nagios告诉我其他3个DC有KCCEvent错误，新机器报告“连接失败”错误。

在新机器上执行dcdiag报告：主机无法parsing为IP地址。当我使用DNS名称login时，这看起来很疯狂。我可以使用这个DNS名称从其他三台机器ping它。

从新机器repadmin /showreps说，看到其他3台机器。从其中一台较旧的机器执行此操作不会显示新机器。

我已经尝试了很多次netdiag /repair 。没有运气。

在任何机器上都没有运行防火墙。

如果我通过MMC（在新计算机上）查看域信息，则显示所有信息都是最新的。用户，计算机，数据中心..在那里。

林不知道我添加这台新机器错过了什么步骤。 build议？

编辑：从非工作的dcdiag：

 C:\Documents and Settings\Administrator.BME>dcdiag Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\YELLOW Starting test: Connectivity The host 312ce6ea-7909-4e15-aff6-45c3d1d9a0d9._msdcs.server.edu could not be resolved to an IP address. Check the DNS server, DHCP, server name, etc Although the Guid DNS name (312ce6ea-7909-4e15-aff6-45c3d1d9a0d9._msdcs.server.edu) couldn't be resolved, the server name (yellow.server.edu) resolved to the IP address (10.127.24.79) and was pingable. Check that the IP address is registered correctly with the DNS server. ......................... YELLOW failed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\YELLOW Skipping all tests, because server YELLOW is not responding to directory service requests Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : bme Starting test: CrossRefValidation ......................... bme passed test CrossRefValidation Starting test: CheckSDRefDom ......................... bme passed test CheckSDRefDom Running enterprise tests on : server.edu Starting test: Intersite ......................... server.edu passed test Intersite Starting test: FsmoCheck ......................... server.edu passed test FsmoCheck dcdiag from working: P:\>dcdiag Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\AD1 Starting test: Connectivity ......................... AD1 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\AD1 Starting test: Replications ......................... AD1 passed test Replications Starting test: NCSecDesc ......................... AD1 passed test NCSecDesc Starting test: NetLogons ......................... AD1 passed test NetLogons Starting test: Advertising ......................... AD1 passed test Advertising Starting test: KnowsOfRoleHolders ......................... AD1 passed test KnowsOfRoleHolders Starting test: RidManager ......................... AD1 passed test RidManager Starting test: MachineAccount ......................... AD1 passed test MachineAccount Starting test: Services ......................... AD1 passed test Services Starting test: ObjectsReplicated ......................... AD1 passed test ObjectsReplicated Starting test: frssysvol ......................... AD1 passed test frssysvol Starting test: frsevent ......................... AD1 passed test frsevent Starting test: kccevent ......................... AD1 passed test kccevent Starting test: systemlog ......................... AD1 passed test systemlog Starting test: VerifyReferences ......................... AD1 passed test VerifyReferences Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : bme Starting test: CrossRefValidation ......................... bme passed test CrossRefValidation Starting test: CheckSDRefDom ......................... bme passed test CheckSDRefDom Running enterprise tests on : server.edu Starting test: Intersite ......................... server.edu passed test Intersite Starting test: FsmoCheck ......................... server.edu passed test FsmoCheck P:\>

检查新DC上的DNS设置; 确保查询本地DNS服务器，并可以parsing其他服务器的名称。你可以解决它的名字并不意味着它可以解决其他区议会的名字，而且有可能是这个问题。

有可能它可以使用NBNS或WINSparsing其他服务器的名称，但不能使用DNS，反之亦然。

编辑：通过上面添加的输出，很明显，这个问题是在DNS中。检查您的DNS服务器上的日志是否有失败的更新等，并确保新的服务器有权进行DNS更改（尽pipe作为DC它应该能够做到这一点）。问题不是服务器的名称不能parsing，而是它的SRVlogging不起作用。

你可以使用dig（使用BIND，unix name守护进程，但是有一个windows版本在某个地方浮动）来检查你得到的IN SRV和IN A 312ce6ea-7909-4e15-aff6-45c3d1d9a0d9._msdcs.server.edu在每个你的DNS服务器上。

不要打扰挖掘或nslookup。只要去DNSpipe理工具，并查找logging的DNS服务器。请执行下列操作：

使用RDPlogin到您的一个DC
启动DNSpipe理工具
点击列表中的DC
点击“正向查找区域”
点击“_msdcs。（你的域名）”

看看右边的条目。你应该为你的每个DC有一个NSlogging和一个CNAMElogging。

validation名称为312ce6ea-7909-4e15-aff6-45c3d1d9a0d9的CNAMElogging，数据是DC的FQDN。

从你所说的话，有问题的DC中缺less了这个logging。在“属性”窗口中确认_msdcs。（您的域）区域已设置为AD集成。