Re: Event 2088 and Event 1960
- From: "Louis" <louis@xxxxxxxxxx>
- Date: Mon, 9 Oct 2006 12:45:07 +0800
Can any experts help on this ?
Really appreciate it. Thanks
--
"Louis" <louis@xxxxxxxxxx> wrote in message
news:ObXbBTr6GHA.4580@xxxxxxxxxxxxxxxxxxxxxxx
Hi Experts
We originally have 1 single DC (Windows 2003 Standard Server) installed on
our network. Recently we have decided to install an additional DC due to
the expansion of our internet network. After the DC was installed and
promoted, everything seems to be working fine except whenever the DC is
restarted a number of 2088 and 1960 events were logged in the Directory
Service log.
-----
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 2088
Date: 6/10/2006
Time: 15:33:27
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC01-DC02
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:
DC01
Failing DNS host name:
ed8b5704-b041-4dc7-ab2e-b34e24f4e8e9._msdcs.mydomain.intra
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.
-----
Event Type: Error
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1960
Date: 6/10/2006
Time: 15:33:39
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC01-DC02
Description:
Internal event: The following domain controller received an exception from
a remote procedure call (RPC) connection. The operation may have failed.
Process ID:
456
Reported error information:
Error value:
Could not find the domain controller for this domain. (1908)
Domain controller:
ed8b5704-b041-4dc7-ab2e-b34e24f4e8e9._msdcs.mydomain.intra
Extended error information:
Error value:
No authority could be contacted for authentication. (2148074257)
Domain controller:
DC01-DC02
Additional Data
Internal ID:
5000bab
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-----
Event Type: Information
Event Source: NTDS General
Event Category: Service Control
Event ID: 1394
Date: 6/10/2006
Time: 15:37:40
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC01-DC02
Description:
All problems preventing updates to the Active Directory Database have been
cleared. New updates to the Active Directory database are succeeding. The
Net Logon service has restarted.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-----
After a series of the above logs, I found the event 1394 as shown below
was logged as well. Can I simply ignore the 2 events earlier ? If so,
what should I do to prevent these warnings/errors from happening ?
Thanks in advance.
--
.
- Follow-Ups:
- Re: Event 2088 and Event 1960
- From: Irwin, MCSE,MCDBA,MCT
- Re: Event 2088 and Event 1960
- References:
- Event 2088 and Event 1960
- From: Louis
- Event 2088 and Event 1960
- Prev by Date: RE: Local Profile Maintenance
- Next by Date: AD without DNS
- Previous by thread: Event 2088 and Event 1960
- Next by thread: Re: Event 2088 and Event 1960
- Index(es):
Relevant Pages
|
Loading
