Exchange灾难恢复之GC转移和ex转移实录

removed or is not replicated from the specified server.
An event ID message that is similar to the following may also be logged in the System event log:

Event ID: 1265
Source: NTDS KCC
Type: Warning
Category: Knowledge Consistency

The attempt to establish a replication link with parameters

Partition: DC=yourinfo,DC=yourinfo,DC=yourinfo,DC=com Source DSA DN: CN=NTDS Settings,CN=NT5-PCI-20,CN=Servers,CN=GSCIntranet,CN=Sites,CN=Configuration,DC=child,DC=yourdomain,DC=com
Source DSA Address:
YourDomainController. YourDomain.com
Inter-site Transport (if any):

failed with the following status:

The DSA operation is unable to proceed because of a DNS lookup failure. The record data
is the status code. This operation will be retried. CAUSE
This issue occurs because the DNS Database does not have a service (SRV) resource record
for the YourDomainController.YourDomain.com domain controller.
RESOLUTION
To resolve this issue, follow these steps:
1. Ping the Domain Controller. To do so, type YourDomainController.YourDomain.com at the
command prompt, and then press ENTER.

If you receive a reply that the ping request could not find the host, the domain controller's
SRV record is not populated in the DNS Database.
2. Check the configuration of DNS and make sure that Allow Dynamic Updates is enabled.
To do this, follow these steps:
1. Click Start, point to Programs, click Administrative Tools, and then click DNS.
2. Expand the DNS folder.
3. Expand the Forward Lookup Zones folder.
4. Right-click the folder, and then click Properties.
5. In the Allow Dynamic Updates box, click Yes.
6. Click OK.
7. Stop and then restart DNS.
3. Stop and then restart the Netlogon service on YourDomainController.

By doing this, you force the domain controller to register the appropriate SRV records. The
change is then replicated to DNS.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 2000.

我检查a的dns-Forward Lookup Zones-Properties,已经是支持动态更新的了,并且我也重启了dns和netlogon服务.但是这个错误event还是每隔十五分钟出现一次.

后来昨天终于发现一些问题了,大家注意事件1265里面得那个: CN=MAILSRV,话说这个mailsrv可有来头,是我来之前那个水货网管建立得一个测试服务器,最早是做单独得dc来用得.然后我到ad站点和域控制台一看,果不其然,有一个site,里面含有两台dc:mailsrv和mailserver.这两台dc现在根本就没有用到了.于是我点击右键删除之….结果提示:无法删除ads组件,狂晕一阵,然后到M$网站找到方法了,装win2k tools,然后用adsi修改,删除里面多余得dc,这样问题解决了,event里面再也没有出现错误提示了.

现在我又开始进行我得初衷:将a彻底得从我得dc群组里面消失掉,发现一旦停掉a,普通用户还是会有那个无法找到exchange得错误.这个时候俺已经豁出去了,深呼吸一下,开始找一些问题点.突然发现在建立用户得时候要选择一个ex得母服务器,难不成是这个原因??于是,我新建一个用户,选择ex服务器是b,关掉a,测试---------各位观众,ok了…一切正常了,那么原来选择exa得用户我可以用exchage

 如果您对本文有任何疑问或者建议，请到讨论区发表您的意见: >> 论坛入口 <<

上一页 1 2 34 下一页

上一篇：MS Exchange Internet 协议   下一篇：Exchange2000灾难恢复实录

【文章评论】 【收藏本文】 【推荐好友】 【打印本文】 【我要投稿】 【论坛讨论】