getting event 2088 after unresponsive system
- From: r. wales <rwales@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 31 May 2006 09:38:01 -0700
I have 3 DC's, two are 2K3 and one is 2K. PDC is 2K3. Last Saturday my PDC
went unresponsive and undiscovered until Tuesday morning. I have managed to
get most things cleaned up (event logs were very ugly). However, this
morning on my 2K3 backup DC I received event 2088 and I am not sure what to
do about it. Replication has occured using NetBIOS, but I would like to get
this taken care of.
Event reads as follows:
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 2088
Date: 5/31/2006
Time: 9:13:43 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: <BackupDCServerName>
Description:
Active Directory could not use DNS to resolve the IP address of the source
domain controller listed below. To maintain the consistency of Security
groups, group policy, users and computers and their passwords, Active
Directory successfully replicated using the NetBIOS or fully qualified
computer name of the source domain controller.
Invalid DNS configuration may be affecting other essential operations on
member computers, domain controllers or application servers in this Active
Directory forest, including logon authentication or access to network
resources.
You should immediately resolve this DNS configuration error so that this
domain controller can resolve the IP address of the source domain controller
using DNS.
Alternate server name:
<PDCServerName>
Failing DNS host name:
<PDCfqdnCNAME>
NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour
period, even if more than 10 failures occur. To log all individual failure
events, set the following diagnostics registry value to 1:
Registry Path:
HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client
User Action:
1) If the source domain controller is no longer functioning or its
operating system has been reinstalled with a different computer name or
NTDSDSA object GUID, remove the source domain controller's metadata with
ntdsutil.exe, using the steps outlined in MSKB article 216498.
2) Confirm that the source domain controller is running Active directory
and is accessible on the network by typing "net view \\<source DC name>" or
"ping <source DC name>".
3) Verify that the source domain controller is using a valid DNS server for
DNS services, and that the source domain controller's host record and CNAME
record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE
available on http://www.microsoft.com/dns
dcdiag /test:dns
4) Verify that that this destination domain controller is using a valid DNS
server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE
command on the console of the destination domain controller, as follows:
dcdiag /test:dns
5) For further analysis of DNS error failures see KB 824449:
http://support.microsoft.com/?kbid=824449
Additional Data
Error value:
11004 The requested name is valid, but no data of the requested type was
found.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I am able to ping back and forth. Nslookup and reverse nslookup seem to be
working fine from both DC's. The 2K box appears to be replicating fine.
Also, about the time my PDC went unresponsive I had this event logged on the
backup DC in question:
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Date: 5/27/2006
Time: 1:53:41 PM
User: N/A
Computer: <BackupDCServerName>
Description:
DNS server has updated its own host (A) records. In order to ensure that
its DS-integrated peer DNS servers are able to replicate with this server, an
attempt was made to update them with the new records through dynamic update.
An error was encountered during this update, the record data is the error
code.
If this DNS server does not have any DS-integrated peers, then this error
should be ignored.
If this DNS server's Active Directory replication partners do not have the
correct IP address(es) for this server, they will be unable to replicate with
it.
To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS
server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this
server.
5) If there are no A records for this server, add at least one A record
corresponding to an address on this server, that the replication partner can
contact. (In other words, if there multiple IP addresses for this DNS
server, add at least one that is on the same network as the Active Directory
DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner. It is
only necessary that the records are fixed up on enough replication partners
so that every server that replicates with this server will receive (through
replication) the new data.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: b4 05 00 00 ´...
I looked through DNS for both PDC and BUDC, they seem to be identical.
Thanks in advance for any info you can give me.
.
- Prev by Date: Re: Alias
- Next by Date: Re: Changing DNS domain name for new AD install
- Previous by thread: Event ID 5719 at boot only
- Next by thread: SOA
- Index(es):
Relevant Pages
|
Loading
