tag:blogger.com,1999:blog-3920347219421157797.post1137929229800012323..comments2024-03-27T21:55:28.163-07:00Comments on Clint Boessen's Blog: AD Replication Issue - The naming context is in the process of being removed or is not replicated from the specified serverClint Boessenhttp://www.blogger.com/profile/11156487394562821934noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-3920347219421157797.post-57916949185566242232015-08-07T07:35:47.196-07:002015-08-07T07:35:47.196-07:00Thanks, had a similar (but not the same issue) but...Thanks, had a similar (but not the same issue) but the fix was the sameStephenhttps://www.blogger.com/profile/14822652759349628552noreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-54552550908932174792013-05-23T20:01:04.053-07:002013-05-23T20:01:04.053-07:00Hi Anonymous,
This customer has over 30 domain co...Hi Anonymous,<br /><br />This customer has over 30 domain controllers so as you would understand the wait would be dependant on replication and the ISTG (part of the KCC) to perform rediscovery.<br /><br />Also thanks for your input Mike.<br /><br />Kind Regards,<br />ClintClint Boessenhttps://www.blogger.com/profile/11156487394562821934noreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-53093203789414561632013-05-23T13:23:06.309-07:002013-05-23T13:23:06.309-07:00Good blog Clint,
For readers that record is also ...Good blog Clint,<br /><br />For readers that record is also referred to as DSA GUID or DC-GUID depending on the search. Probably the most important record in DNS.<br /><br />Thanks<br /><br />MikeMike Klinehttp://www.adisfun.comnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-70099343122927417892013-05-23T12:32:20.909-07:002013-05-23T12:32:20.909-07:00Sorry, I just missed that you manually re-created ...Sorry, I just missed that you manually re-created the GUID entry. Isn't there an automatic way of doing this, for example when the Netlogon/ADDS/DNS service is restarted, it checks for this issue and fixes all by itself?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-11133437236764925962013-05-23T12:09:13.503-07:002013-05-23T12:09:13.503-07:00"After 45 minutes replication began working a..."After 45 minutes replication began working again for DC1."<br /><br />So the system fixed itself automatically after 45mins, or you had to actually do something to fix it? If you had to do, then what actually? If you had waited more than 45 mins, and the issue would have been resolved all by itself, would you even notice this transient issue at all?Anonymousnoreply@blogger.com