Re: netdiag error

Tech-Archive recommends: Fix windows errors by optimizing your registry

Is this a promotion or a demotion?

"Woolpert" <alert.manager@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6366C3A6-BC8F-4E06-B0C2-D9A4EE1A6C6C@xxxxxxxxxxxxxxxx
> 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: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: This machine is not working properly as a DC.
    ... Ethernet adapter Server Local Area Connection: ... Connection-specific DNS Suffix. ... event id 2008 source ntds replication, category ds rpc client, user NT ... computer name of the source domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: GPOs Not Replicating
    ... I've tried the file creation, gave it an hour, no replication.. ... Services could not resolve the following DNS host name of the source ... domain controller is running Active Directory Domain Services and is ... controller is using a valid DNS server for DNS services, ...
    (microsoft.public.windows.server.active_directory)
  • Re: multiple errors in Active Directory
    ... Connection-specific DNS suffix: ... If this computer is a domain controller for the specified domain, ... The attempt to establish a replication link for the following writable ... DNS server has updated its own host records. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication of password resets/unlocks
    ... First off, I know it isn't your fault, but the name urgent replication implies something that it isn't guaranteed to be. ... So if you hit a bridgehead that is backed up with inbound replication requests, even though the request was urgently queued, it can take awhile for that information to get into the bridgehead and then replicated back out. ... Urgent replication is implemented immediately by using RPC/IP to notify replication partners that changes have occurred on a source domain controller. ... In Active Directory domains, a single domain controller in each domain holds the role of PDC emulator, which simulates the behavior of a Windows NT version 3.x-based or Windows NT 4.0-based PDC. ...
    (microsoft.public.windows.server.active_directory)