Re: netdiag error

We first got this error when we tried adding the domain controller a week
ago. The error below is from running netdiag /test:dns yesterday. The only
message that we are getting in the event log is below. But as you can see
this is from the 16th of December and today is the 28th. I don't notice any
other issues, so I don't know if this is really causing a problem or not?

Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 2023
Date: 12/16/2005
Time: 1:36:39 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: AD75DC1
Description:
The local domain controller was unable to replicate changes to the following
remote domain controller for the following directory partition.

Remote domain controller:
9474bfa3-2ad4-4bd3-842f-b8cc26cd228d._msdcs.Woolpertinc.local
Directory partition:
CN=Schema,CN=Configuration,DC=Woolpertinc,DC=local

The local domain controller cannot complete demotion.

User Action
Investigate why replication between these two domain controllers cannot be
performed. Then, try to demote this domain controller again.

Additonal Data
Error value:
8524 The DSA operation is unable to proceed because of a DNS lookup failure.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


"Al Mulnick" wrote:

> Wait for 30 minutes?
> If not, can you manually verify the addresses using NSLOOKUP?
> Having the records on the OS aren't nearly as important as having them on
> the 172.22.85.66 & 172.22.85.197 servers. Ensure they're registered
> appropriately and wait the 30 minutes. Check again. Is it still unable to
> replicate?
>
> Al
>
>
> "Woolpert" <alert.manager@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:C492B47C-72CE-40EB-8D29-B8ADFF0B4714@xxxxxxxxxxxxxxxx
> >I tried to join an additonal DC to AD, but it gets an error when trying to
> > replicate. I then tried to remove the DC from AD and I get the following
> > eror when I test DNS using netdiag.
> >
> > DNS test . . . . . . . . . . . . . : Failed
> > [WARNING] The DNS entries for this DC are not registered correctly on
> > DNS server '172.22.85.66'. Please wait for 30 minutes for DNS server
> > replication.
> > [WARNING] The DNS entries for this DC are not registered correctly on
> > DNS server '172.22.85.197'. Please wait for 30 minutes for DNS server
> > replication.
> > [FATAL] No DNS servers have the DNS records for this DC registered.
> >
> >
> > I have turned on dynamic updates on the dns zones that this machine would
> > talk to and it appears that all of the DNS entries that are located in the
> > file: %WINDIR%\system32\config\netlogon.dns have been successfully created
> > and replicated to the 2 other domain controllers in our environment.
> >
> > Any suggestions?
>
>
>
.

Relevant Pages

  • Re: Changing FSMO Schema Owner
    ... I can now Replicate Now fine both ways on both DCs ... In ADSIedit on MAYA there was no sign of INCA but on AZTEC there was CN=INCA ... INCA was an old DNS Server. ... If the old domain controller was a DNS server, ...
    (microsoft.public.windows.server.active_directory)
  • Re: win 2k3 enterprise fault tolerant dns
    ... > I am setting up the second domain controller for my new domain ... > components added dns and restarted the server. ... > opened up the dns tool, that I would have to add a secondary zone ... AD zones will replicate to all Domain Controllers in the domain by default, ...
    (microsoft.public.windows.server.dns)
  • Re: How to rebuild a single AD... Please Help...
    ... I now need to make it a DNS.. ... how will the DNS replicate with the existing DNS server on the ... changing the DNS server for each machine.. ... Also how easy is it to demote the domain controller.. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Second DNS Server
    ... I just backed up my domain controller tonight, installed dns after reboot ... >> to the backup domain controller OK so all seems to be well there. ... > The zone will replicate to at least all DCs, ...
    (microsoft.public.windows.server.dns)
  • Re: DCs not Replicating
    ... When you demoted the Domain Controller was it successful? ... DNS, GC, DHCP, etc? ... Do you have a Global Catalog Server? ... did you give AD enough time to replicate the removal of ...
    (microsoft.public.windows.server.active_directory)