Re: NTDS Replication
- From: leopete <leopete@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 3 Oct 2007 12:02:01 -0700
This is on the our domain controller...This error happens on the other servers
C:\Documents and Settings\Administrator>dcdiag
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\MANGO
Starting test: Connectivity
......................... MANGO passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\MANGO
Starting test: Replications
[Replications Check,MANGO] A recent replication attempt failed:
From LIBSRVR to MANGO
Naming Context: DC=ForestDnsZones,DC=agawam-ma,DC=com
The replication generated an error (1256):
The remote system is not available. For information about
network tr
oubleshooting, see Windows Help.
The failure occurred at 2007-10-03 14:00:10.
The last success occurred at 2007-08-08 13:20:18.
1348 failures have occurred since the last success.
[LIBSRVR] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
[Replications Check,MANGO] A recent replication attempt failed:
From LIBSRVR to MANGO
Naming Context: CN=Schema,CN=Configuration,DC=agawam-ma,DC=com
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2007-10-03 14:00:31.
The last success occurred at 2007-08-01 13:54:33.
1515 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,MANGO] A recent replication attempt failed:
From LIBSRVR to MANGO
Naming Context: CN=Configuration,DC=agawam-ma,DC=com
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2007-10-03 14:00:10.
The last success occurred at 2007-08-01 13:54:53.
1515 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,MANGO] A recent replication attempt failed:
From LIBSRVR to MANGO
Naming Context: DC=lib,DC=agawam-ma,DC=com
The replication generated an error (1256):
The remote system is not available. For information about
network tr
oubleshooting, see Windows Help.
The failure occurred at 2007-10-03 14:00:10.
The last success occurred at 2007-08-08 13:21:14.
1348 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
MANGO: Current time is 2007-10-03 14:55:09.
DC=ForestDnsZones,DC=agawam-ma,DC=com
Last replication recieved from LIBSRVR at 2007-08-08 13:20:00.
CN=Schema,CN=Configuration,DC=agawam-ma,DC=com
Last replication recieved from LIBSRVR at 2007-08-01 13:54:33.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
CN=Configuration,DC=agawam-ma,DC=com
Last replication recieved from LIBSRVR at 2007-08-01 13:54:56.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
DC=lib,DC=agawam-ma,DC=com
Last replication recieved from LIBSRVR at 2007-08-08 13:20:57.
......................... MANGO passed test Replications
Starting test: NCSecDesc
......................... MANGO passed test NCSecDesc
Starting test: NetLogons
......................... MANGO passed test NetLogons
Starting test: Advertising
......................... MANGO passed test Advertising
Starting test: KnowsOfRoleHolders
......................... MANGO passed test KnowsOfRoleHolders
Starting test: RidManager
......................... MANGO passed test RidManager
Starting test: MachineAccount
......................... MANGO passed test MachineAccount
Starting test: Services
......................... MANGO passed test Services
Starting test: ObjectsReplicated
......................... MANGO passed test ObjectsReplicated
Starting test: frssysvol
......................... MANGO passed test frssysvol
Starting test: frsevent
......................... MANGO passed test frsevent
Starting test: kccevent
......................... MANGO passed test kccevent
Starting test: systemlog
......................... MANGO passed test systemlog
Starting test: VerifyReferences
......................... MANGO passed test VerifyReferences
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : agawam-ma
Starting test: CrossRefValidation
......................... agawam-ma passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... agawam-ma passed test CheckSDRefDom
Running enterprise tests on : agawam-ma.com
Starting test: Intersite
......................... agawam-ma.com passed test Intersite
Starting test: FsmoCheck
......................... agawam-ma.com passed test FsmoCheck
C:\Documents and Settings\Administrator>
--
The only easy day was Yesterday
"Mathieu CHATEAU" wrote:
can you launch and post result of:DNS Host Name: mango.agawam-ma.com
dcdiag
netdiag
netdom query fsmo
thanks
--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr
"leopete" <leopete@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F33D79D2-E620-4653-B7F0-CFDA106BF083@xxxxxxxxxxxxxxxx
The server has been up and users have been loogging in.
--
The only easy day was Yesterday
"Mathieu CHATEAU" wrote:
Hello,
it doesn't seem as indicate the log, it's just one month since the last
replication:
More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
0
More than a tombstone lifetime:
0
Tombstone lifetime (days):
60
--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr
"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb665cfa28c9d406e5f42f00@xxxxxxxxxxxxxxxxxxxxxxx
Hello leopete,
Seems that the server is disconnected from the domain over tombstone
lifetime period.
http://eventid.net/display.asp?eventid=1864&eventno=4849&source=NTDS%20Replication&phase=1
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
HelloComputer Name: MANGO
I recently took on responsibly on an existing server. Looking over the
event
viewer i see the following error in directory services
Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1864
Date: 10/2/2007
Time: 4:44:36 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: MANGO
Description:
This is the replication status for the following directory partition
on the
local domain controller.
Directory partition:
DC=ForestDnsZones,DC=RootDomain,DC=com
The local domain controller has not recently received replication
information from a number of domain controllers. The count of domain
controllers is shown, divided into the following intervals.
More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
0
More than a tombstone lifetime:
0
Tombstone lifetime (days):
60
Domain controllers that do not replicate in a timely manner may
encounter
errors. It may miss password changes and be unable to authenticate. A
DC that
has not replicated in a tombstone lifetime may have missed the
deletion of some objects, and may be automatically blocked from future
replication until it is reconciled.
To identify the domain controllers by name, install the support tools
included on the installation CD and run dcdiag.exe. You can also use
the support tool repadmin.exe to display the replication latencies of
the domain controllers in the forest. The command is "repadmin
/showvector /latency <partition-dn>".
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
System info : Microsoft Windows Server 2003 R2 (Build 3790)
Processor : x86 Family 15 Model 4 Stepping 10, GenuineIntel
List of installed hotfixes :
KB925398_WMP64
KB925902
KB927891
KB929123
KB929969
KB930178
KB931784
KB931836
KB932168
KB933566-IE7
KB935839
KB935840
KB935966
Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
Adapter : Local Area Connection
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : mango
IP Address . . . . . . . . : 192.168.25.5
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.25.254
Dns Servers. . . . . . . . : 192.168.25.5
192.168.25.7
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenge
r Service', <20> 'WINS' names is missing.
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{59D76296-4DF7-4371-A709-B4048BE814D6}
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation
Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'192.168.25.5
' and other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server
'192.168.25.7
' and other DCs also have some of the names registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{59D76296-4DF7-4371-A709-B4048BE814D6}
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{59D76296-4DF7-4371-A709-B4048BE814D6}
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Skipped
Note: run "netsh ipsec dynamic show /?" for more detailed information
.
- Follow-Ups:
- Re: NTDS Replication
- From: leopete
- Re: NTDS Replication
- From: Mathieu CHATEAU
- Re: NTDS Replication
- From: Meinolf Weber
- Re: NTDS Replication
- References:
- Re: NTDS Replication
- From: Meinolf Weber
- Re: NTDS Replication
- From: Mathieu CHATEAU
- Re: NTDS Replication
- From: leopete
- Re: NTDS Replication
- From: Mathieu CHATEAU
- Re: NTDS Replication
- Prev by Date: Re: Administrative Templates not showing registry entries
- Next by Date: Re: NTDS Replication
- Previous by thread: Re: NTDS Replication
- Next by thread: Re: NTDS Replication
- Index(es):
Relevant Pages
|
Loading