Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Active Directory » New DC problem with event log NTDS Replication error 1864
New DC problem with event log NTDS Replication error 1864 [message #371455] Tue, 19 January 2010 00:08 Go to next message
Jason Huang  is currently offline Jason Huang  Taiwan
Messages: 60
Registered: September 2009
Member
Hi,

I Just promoted a member server to our AD as the 2nd DC( IP:192.168.1.15)
The new DC's LAN setting is as

IP 192.168.1.15/255.255.0.0
DNS:192.168.1.1

The IP 192.168.1.1 is the 1st DC in our domain Mycom.com.
The 1st and 2nd DC are Windows 2003 Server and Windows 2003 Server R2
respectively.

However, there's no DNS Server ruuning on the 2nd DC, I'm wondering if the
is normal or not.
Also, the 2nd DC's windows firewall is currently OFF, is this safe enough
for a DC?

I looked up the event viewer of the 2nd DC and found a NTDS Replication
error 1864 with user NT AUTHORITY\ANONYMOUS LOGON.
When I added an new user from the 1st DC for my domain, the new created
account doesn't show up on the 2nd DC user list.
How do I fix these questions?
Thanks for help.


Jason
Re: New DC problem with event log NTDS Replication error 1864 [message #371458 is a reply to message #371455] Tue, 19 January 2010 00:19 Go to previous messageGo to next message
meiweb  is currently offline meiweb  Germany
Messages: 2225
Registered: September 2009
Senior Member
Hello Jason,

Is this a follow up from "Default-First-Site-Name / Servers and DNS question"
on 11.Jan.2010?

As you said in the previous posting that server was a DC already before,
did you ever removed it complete from the AD database before promoting again?

Please post an unedited ipconfig /all from all 3 DCs and also the repadmin
/showrepl from each one.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi,
>
> I Just promoted a member server to our AD as the 2nd DC(
> IP:192.168.1.15) The new DC's LAN setting is as
>
> IP 192.168.1.15/255.255.0.0
> DNS:192.168.1.1
> The IP 192.168.1.1 is the 1st DC in our domain Mycom.com.
> The 1st and 2nd DC are Windows 2003 Server and Windows 2003 Server R2
> respectively.
> However, there's no DNS Server ruuning on the 2nd DC, I'm wondering if
> the
> is normal or not.
> Also, the 2nd DC's windows firewall is currently OFF, is this safe
> enough
> for a DC?
> I looked up the event viewer of the 2nd DC and found a NTDS
> Replication
> error 1864 with user NT AUTHORITY\ANONYMOUS LOGON.
> When I added an new user from the 1st DC for my domain, the new
> created
> account doesn't show up on the 2nd DC user list.
> How do I fix these questions?
> Thanks for help.
> Jason
>
Re: New DC problem with event log NTDS Replication error 1864 [message #371486 is a reply to message #371458] Tue, 19 January 2010 01:49 Go to previous messageGo to next message
Jason Huang  is currently offline Jason Huang  Taiwan
Messages: 60
Registered: September 2009
Member
Yes sir, they are all the servers/member server/ dc we discussed before.

The M00S is now a member server only.
We have the MIS, Sun, V00S three DCs, while the V00S is in charge of the sub
domain v00domain, and the Sun is the newly added DC.
I can run the repadmin / showrepl only on the MIS(root DC), not on the other
2 DCs.
Thanks for help.


The repadmin / showrepl output is as

repadmin running command /showrepl against server localhost

Default-First-Site-Name\MIS

DC Options: IS_GC
Site Options: (none)
DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
DC invocationID: 79a17049-d367-4f70-a060-9c199120ac3e

==== INBOUND NEIGHBORS ======================================


DC=MyCom,DC=com

Default-First-Site-Name\SUN via RPC

DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-19 15:58:44 was successful.

CN=Configuration,DC=MyCom,DC=com

Default-First-Site-Name\M00S via RPC
DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
Last attempt @ 2010-01-19 15:55:11 failed, result 1753 (0x6d9):

There are no more endpoints available from the endpoint mapper

33140 consecutive failure(s).
Last success @ 1983-06-18 18:17:20.

Default-First-Site-Name\V00S via RPC

DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-19 15:55:11 was delayed for a normal reason,
result 8418 (0x20e2):

The replication operation failed because of a schema mismatch between
the servers involved."

Last success @ 2010-01-19 10:55:12.

Default-First-Site-Name\SUN via RPC

DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-19 16:00:52 was successful.


CN=Schema,CN=Configuration,DC=MyCom,DC=com

Default-First-Site-Name\V00S via RPC
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-19 15:55:11 was successful.

Default-First-Site-Name\M00S via RPC
DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
Last attempt @ 2010-01-19 15:55:11 failed, result 1753 (0x6d9):

There are no more endpoints available from the endpoint mapper

15943 consecutive failure(s).

Last success @ 1983-06-18 17:47:59.

Default-First-Site-Name\SUN via RPC
DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-19 15:55:11 was successful.


DC=m00domain,DC=MyCom,DC=com

Default-First-Site-Name\M00S via RPC
DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
Last attempt @ 2010-01-19 15:55:11 failed, result 1256 (0x4e8):

The remote system is not available. For information about
network troubleshooting, see Windows Help.

18255 consecutive failure(s).
Last success @ 1983-06-18 17:52:27.


DC=V00Domain,DC=MyCom,DC=com

Default-First-Site-Name\V00S via RPC

DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48

Last attempt @ 2010-01-19 15:55:11 was delayed for a normal reason,
result 8418 (0x20e2):

The replication operation failed because of a schema mismatch between
the servers involved."

Last success @ 2010-01-19 10:55:12.


Source: Default-First-Site-Name\M00S

******* 33140 CONSECUTIVE FAILURES since 1983-06-18 18:17:20

Last error: 1256 (0x4e8):

The remote system is not available. For information about
network troubleshooting, see Windows Help.








"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de>
???????:6cb2911dc7df8cc66f74083d8b8@msnews.microsoft.com...
> Hello Jason,
>
> Is this a follow up from "Default-First-Site-Name / Servers and DNS
> question" on 11.Jan.2010?
>
> As you said in the previous posting that server was a DC already before,
> did you ever removed it complete from the AD database before promoting
> again?
>
> Please post an unedited ipconfig /all from all 3 DCs and also the repadmin
> /showrepl from each one.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Hi,
>>
>> I Just promoted a member server to our AD as the 2nd DC(
>> IP:192.168.1.15) The new DC's LAN setting is as
>>
>> IP 192.168.1.15/255.255.0.0
>> DNS:192.168.1.1
>> The IP 192.168.1.1 is the 1st DC in our domain Mycom.com.
>> The 1st and 2nd DC are Windows 2003 Server and Windows 2003 Server R2
>> respectively.
>> However, there's no DNS Server ruuning on the 2nd DC, I'm wondering if
>> the
>> is normal or not.
>> Also, the 2nd DC's windows firewall is currently OFF, is this safe
>> enough
>> for a DC?
>> I looked up the event viewer of the 2nd DC and found a NTDS
>> Replication
>> error 1864 with user NT AUTHORITY\ANONYMOUS LOGON.
>> When I added an new user from the 1st DC for my domain, the new
>> created
>> account doesn't show up on the 2nd DC user list.
>> How do I fix these questions?
>> Thanks for help.
>> Jason
>>
>
>
Re: New DC problem with event log NTDS Replication error 1864 [message #371540 is a reply to message #371486] Tue, 19 January 2010 04:25 Go to previous messageGo to next message
meiweb  is currently offline meiweb  Germany
Messages: 2225
Registered: September 2009
Senior Member
Hello Jason,

Please again post the complete ipconfig /all form all 3 DCs.

To run repadmin you have to install on the other DCs the support\tools\suptools.msi
from the 2003 installation disk.

Is the new Windows server 2003 R2 and did you upgrade the schema on the existing
DC with the schema master FSMO, check with "schupgr" in a command prompt
which server it is?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Yes sir, they are all the servers/member server/ dc we discussed
> before.
>
> The M00S is now a member server only.
> We have the MIS, Sun, V00S three DCs, while the V00S is in charge of
> the sub
> domain v00domain, and the Sun is the newly added DC.
> I can run the repadmin / showrepl only on the MIS(root DC), not on the
> other
> 2 DCs.
> Thanks for help.
> The repadmin / showrepl output is as
>
> repadmin running command /showrepl against server localhost
>
> Default-First-Site-Name\MIS
>
> DC Options: IS_GC
> Site Options: (none)
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
> DC invocationID: 79a17049-d367-4f70-a060-9c199120ac3e
> ==== INBOUND NEIGHBORS ======================================
>
> DC=MyCom,DC=com
>
> Default-First-Site-Name\SUN via RPC
>
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> Last attempt @ 2010-01-19 15:58:44 was successful.
> CN=Configuration,DC=MyCom,DC=com
>
> Default-First-Site-Name\M00S via RPC
> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
> Last attempt @ 2010-01-19 15:55:11 failed, result 1753
> (0x6d9):
> There are no more endpoints available from the endpoint
> mapper
>
> 33140 consecutive failure(s).
> Last success @ 1983-06-18 18:17:20.
> Default-First-Site-Name\V00S via RPC
>
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> Last attempt @ 2010-01-19 15:55:11 was delayed for a normal
> reason,
> result 8418 (0x20e2):
> The replication operation failed because of a schema mismatch
> between the servers involved."
>
> Last success @ 2010-01-19 10:55:12.
>
> Default-First-Site-Name\SUN via RPC
>
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> Last attempt @ 2010-01-19 16:00:52 was successful.
> CN=Schema,CN=Configuration,DC=MyCom,DC=com
>
> Default-First-Site-Name\V00S via RPC
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> Last attempt @ 2010-01-19 15:55:11 was successful.
> Default-First-Site-Name\M00S via RPC
> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
> Last attempt @ 2010-01-19 15:55:11 failed, result 1753
> (0x6d9):
> There are no more endpoints available from the endpoint
> mapper
>
> 15943 consecutive failure(s).
>
> Last success @ 1983-06-18 17:47:59.
>
> Default-First-Site-Name\SUN via RPC
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> Last attempt @ 2010-01-19 15:55:11 was successful.
> DC=m00domain,DC=MyCom,DC=com
>
> Default-First-Site-Name\M00S via RPC
> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
> Last attempt @ 2010-01-19 15:55:11 failed, result 1256
> (0x4e8):
> The remote system is not available. For information about
> network troubleshooting, see Windows Help.
>
> 18255 consecutive failure(s).
> Last success @ 1983-06-18 17:52:27.
> DC=V00Domain,DC=MyCom,DC=com
>
> Default-First-Site-Name\V00S via RPC
>
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
>
> Last attempt @ 2010-01-19 15:55:11 was delayed for a normal
> reason, result 8418 (0x20e2):
>
> The replication operation failed because of a schema mismatch
> between the servers involved."
>
> Last success @ 2010-01-19 10:55:12.
>
> Source: Default-First-Site-Name\M00S
>
> ******* 33140 CONSECUTIVE FAILURES since 1983-06-18 18:17:20
>
> Last error: 1256 (0x4e8):
>
> The remote system is not available. For information about
> network troubleshooting, see Windows Help.
>
> "Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de>
> ???????:6cb2911dc7df8cc66f74083d8b8@msnews.microsoft.com...
>
>> Hello Jason,
>>
>> Is this a follow up from "Default-First-Site-Name / Servers and DNS
>> question" on 11.Jan.2010?
>>
>> As you said in the previous posting that server was a DC already
>> before, did you ever removed it complete from the AD database before
>> promoting again?
>>
>> Please post an unedited ipconfig /all from all 3 DCs and also the
>> repadmin /showrepl from each one.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Hi,
>>>
>>> I Just promoted a member server to our AD as the 2nd DC(
>>> IP:192.168.1.15) The new DC's LAN setting is as
>>>
>>> IP 192.168.1.15/255.255.0.0
>>> DNS:192.168.1.1
>>> The IP 192.168.1.1 is the 1st DC in our domain Mycom.com.
>>> The 1st and 2nd DC are Windows 2003 Server and Windows 2003 Server
>>> R2
>>> respectively.
>>> However, there's no DNS Server ruuning on the 2nd DC, I'm wondering
>>> if
>>> the
>>> is normal or not.
>>> Also, the 2nd DC's windows firewall is currently OFF, is this safe
>>> enough
>>> for a DC?
>>> I looked up the event viewer of the 2nd DC and found a NTDS
>>> Replication
>>> error 1864 with user NT AUTHORITY\ANONYMOUS LOGON.
>>> When I added an new user from the 1st DC for my domain, the new
>>> created
>>> account doesn't show up on the 2nd DC user list.
>>> How do I fix these questions?
>>> Thanks for help.
>>> Jason
Re: New DC problem with event log NTDS Replication error 1864 [message #371619 is a reply to message #371455] Tue, 19 January 2010 06:22 Go to previous messageGo to next message
pbbergs  is currently offline pbbergs  United States
Messages: 1024
Registered: July 2009
Senior Member
I would agree with Meinolf that you should post an unedited ipconfig /all
from both dc's so we can look at the definitions. We need to compare subnet
mask, gateway, number of nic's present, dns server, etc...

Also, run diagnostics against your Active Directory domain.

If you don't have the support tools installed, install them from your server
install disk.
d:\support\tools\setup.exe

Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
-> ntfrsutl ds your_dc_name > c:\sysvol.log
-> dnslint /ad /s "ip address of your dc"

**Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take into
account slow links to dc's will also add to the testing time.

If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests without
having to learn all the switch options. The details will be output in
notepad text files that pop up automagically.

The script is located on my website at
http://www.pbbergs.com/windows/downloads.htm

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.

Description and download for dnslint
http://support.microsoft.com/kb/321045

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"Jason Huang" <JasonHuang8888@hotmail.com> wrote in message
news:%23U9IGZNmKHA.6096@TK2MSFTNGP02.phx.gbl...
> Hi,
>
> I Just promoted a member server to our AD as the 2nd DC( IP:192.168.1.15)
> The new DC's LAN setting is as
>
> IP 192.168.1.15/255.255.0.0
> DNS:192.168.1.1
>
> The IP 192.168.1.1 is the 1st DC in our domain Mycom.com.
> The 1st and 2nd DC are Windows 2003 Server and Windows 2003 Server R2
> respectively.
>
> However, there's no DNS Server ruuning on the 2nd DC, I'm wondering if the
> is normal or not.
> Also, the 2nd DC's windows firewall is currently OFF, is this safe enough
> for a DC?
>
> I looked up the event viewer of the 2nd DC and found a NTDS Replication
> error 1864 with user NT AUTHORITY\ANONYMOUS LOGON.
> When I added an new user from the 1st DC for my domain, the new created
> account doesn't show up on the 2nd DC user list.
> How do I fix these questions?
> Thanks for help.
>
>
> Jason
>
>
Re: New DC problem with event log NTDS Replication error 1864 [message #372278 is a reply to message #371540] Tue, 19 January 2010 18:57 Go to previous messageGo to next message
Jason Huang  is currently offline Jason Huang  Taiwan
Messages: 60
Registered: September 2009
Member
Thanks.
The output for the ipconfig of these 3 DC( mis, Sun, V00s) are

Windows IP Configuration

Host Name . . . . . . . . . . . . : mis
Primary Dns Suffix . . . . . . . : MyCom.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : MyCom.com
com

Ethernet adapter ????:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/10 MT Network Connection
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 192.168.0.51
DNS Servers . . . . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . . . . : 192.168.0.200


Windows IP Configuration


Host Name . . . . . . . . . . . . : Sun
Primary Dns Suffix . . . . . . . : MyCom.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : MyCom.com
com


Ethernet adapter ???? 2:


Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/10 EB Network Connection
with I/O Acceleration #2

Physical Address. . . . . . . . . : **-**-**-**-**-**
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.15
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 192.168.0.51
DNS Servers . . . . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . . . . : 192.168.0.200


Windows IP Configuration

Host Name . . . . . . . . . . . . : v00s
Primary Dns Suffix . . . . . . . : V00Domain.MyCom.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : V00Domain.MyCom.com
MyCom.com
com

Ethernet adapter ????:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/10 CT Network Connection
Physical Address. . . . . . . . . : yy-yy-yy-yy-yy-yy
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.25.253
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 192.168.0.51
DNS Servers . . . . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . . . . : 192.168.0.200




"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de>
???????:6cb2911dc8018cc6719a28ab932@msnews.microsoft.com...
> Hello Jason,
>
> Please again post the complete ipconfig /all form all 3 DCs.
>
> To run repadmin you have to install on the other DCs the
> support\tools\suptools.msi from the 2003 installation disk.
>
> Is the new Windows server 2003 R2 and did you upgrade the schema on the
> existing DC with the schema master FSMO, check with "schupgr" in a command
> prompt which server it is?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Yes sir, they are all the servers/member server/ dc we discussed
>> before.
>>
>> The M00S is now a member server only.
>> We have the MIS, Sun, V00S three DCs, while the V00S is in charge of
>> the sub
>> domain v00domain, and the Sun is the newly added DC.
>> I can run the repadmin / showrepl only on the MIS(root DC), not on the
>> other
>> 2 DCs.
>> Thanks for help.
>> The repadmin / showrepl output is as
>>
>> repadmin running command /showrepl against server localhost
>>
>> Default-First-Site-Name\MIS
>>
>> DC Options: IS_GC
>> Site Options: (none)
>> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
>> DC invocationID: 79a17049-d367-4f70-a060-9c199120ac3e
>> ==== INBOUND NEIGHBORS ======================================
>>
>> DC=MyCom,DC=com
>>
>> Default-First-Site-Name\SUN via RPC
>>
>> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
>> Last attempt @ 2010-01-19 15:58:44 was successful.
>> CN=Configuration,DC=MyCom,DC=com
>>
>> Default-First-Site-Name\M00S via RPC
>> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
>> Last attempt @ 2010-01-19 15:55:11 failed, result 1753
>> (0x6d9):
>> There are no more endpoints available from the endpoint
>> mapper
>>
>> 33140 consecutive failure(s).
>> Last success @ 1983-06-18 18:17:20.
>> Default-First-Site-Name\V00S via RPC
>>
>> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
>> Last attempt @ 2010-01-19 15:55:11 was delayed for a normal
>> reason,
>> result 8418 (0x20e2):
>> The replication operation failed because of a schema mismatch
>> between the servers involved."
>>
>> Last success @ 2010-01-19 10:55:12.
>>
>> Default-First-Site-Name\SUN via RPC
>>
>> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
>> Last attempt @ 2010-01-19 16:00:52 was successful.
>> CN=Schema,CN=Configuration,DC=MyCom,DC=com
>>
>> Default-First-Site-Name\V00S via RPC
>> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
>> Last attempt @ 2010-01-19 15:55:11 was successful.
>> Default-First-Site-Name\M00S via RPC
>> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
>> Last attempt @ 2010-01-19 15:55:11 failed, result 1753
>> (0x6d9):
>> There are no more endpoints available from the endpoint
>> mapper
>>
>> 15943 consecutive failure(s).
>>
>> Last success @ 1983-06-18 17:47:59.
>>
>> Default-First-Site-Name\SUN via RPC
>> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
>> Last attempt @ 2010-01-19 15:55:11 was successful.
>> DC=m00domain,DC=MyCom,DC=com
>>
>> Default-First-Site-Name\M00S via RPC
>> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
>> Last attempt @ 2010-01-19 15:55:11 failed, result 1256
>> (0x4e8):
>> The remote system is not available. For information about
>> network troubleshooting, see Windows Help.
>>
>> 18255 consecutive failure(s).
>> Last success @ 1983-06-18 17:52:27.
>> DC=V00Domain,DC=MyCom,DC=com
>>
>> Default-First-Site-Name\V00S via RPC
>>
>> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
>>
>> Last attempt @ 2010-01-19 15:55:11 was delayed for a normal
>> reason, result 8418 (0x20e2):
>>
>> The replication operation failed because of a schema mismatch
>> between the servers involved."
>>
>> Last success @ 2010-01-19 10:55:12.
>>
>> Source: Default-First-Site-Name\M00S
>>
>> ******* 33140 CONSECUTIVE FAILURES since 1983-06-18 18:17:20
>>
>> Last error: 1256 (0x4e8):
>>
>> The remote system is not available. For information about
>> network troubleshooting, see Windows Help.
>>
>> "Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de>
>> ???????:6cb2911dc7df8cc66f74083d8b8@msnews.microsoft.com...
>>
>>> Hello Jason,
>>>
>>> Is this a follow up from "Default-First-Site-Name / Servers and DNS
>>> question" on 11.Jan.2010?
>>>
>>> As you said in the previous posting that server was a DC already
>>> before, did you ever removed it complete from the AD database before
>>> promoting again?
>>>
>>> Please post an unedited ipconfig /all from all 3 DCs and also the
>>> repadmin /showrepl from each one.
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers no rights.
>>> ** Please do NOT email, only reply to Newsgroups
>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> Hi,
>>>>
>>>> I Just promoted a member server to our AD as the 2nd DC(
>>>> IP:192.168.1.15) The new DC's LAN setting is as
>>>>
>>>> IP 192.168.1.15/255.255.0.0
>>>> DNS:192.168.1.1
>>>> The IP 192.168.1.1 is the 1st DC in our domain Mycom.com.
>>>> The 1st and 2nd DC are Windows 2003 Server and Windows 2003 Server
>>>> R2
>>>> respectively.
>>>> However, there's no DNS Server ruuning on the 2nd DC, I'm wondering
>>>> if
>>>> the
>>>> is normal or not.
>>>> Also, the 2nd DC's windows firewall is currently OFF, is this safe
>>>> enough
>>>> for a DC?
>>>> I looked up the event viewer of the 2nd DC and found a NTDS
>>>> Replication
>>>> error 1864 with user NT AUTHORITY\ANONYMOUS LOGON.
>>>> When I added an new user from the 1st DC for my domain, the new
>>>> created
>>>> account doesn't show up on the 2nd DC user list.
>>>> How do I fix these questions?
>>>> Thanks for help.
>>>> Jason
>
>
Re: New DC problem with event log NTDS Replication error 1864 [message #372317 is a reply to message #371540] Tue, 19 January 2010 19:58 Go to previous messageGo to next message
Jason Huang  is currently offline Jason Huang  Taiwan
Messages: 60
Registered: September 2009
Member
I run the command schupgr on the root DC MIS.
The output is:

Opened Connection to MIS
SSPI Bind succeeded
Found Naming Context DC=MyCom,DC=com,DC=tw
Found Naming Context CN=Schema,CN=Configuration,DC=MyCom,DC=com,DC=tw
Found Naming Context CN=Configuration,DC=MyCom,DC=com,DC=tw
Current Schema Version is 31
Upgrading schema to version 31
Schema updated. Rerun setup to upgrade this DC.


The schupgr output for the newly promoted Win2003 R2:

Opened Connection to SUN
SSPI Bind succeeded
Current Schema Version is 31
ERROR: Cannot obtain schema version to upgrade to: 1



"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de>
???????:6cb2911dc8018cc6719a28ab932@msnews.microsoft.com...
> Hello Jason,
>
> Please again post the complete ipconfig /all form all 3 DCs.
>
> To run repadmin you have to install on the other DCs the
> support\tools\suptools.msi from the 2003 installation disk.
>
> Is the new Windows server 2003 R2 and did you upgrade the schema on the
> existing DC with the schema master FSMO, check with "schupgr" in a command
> prompt which server it is?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Yes sir, they are all the servers/member server/ dc we discussed
>> before.
>>
>> The M00S is now a member server only.
>> We have the MIS, Sun, V00S three DCs, while the V00S is in charge of
>> the sub
>> domain v00domain, and the Sun is the newly added DC.
>> I can run the repadmin / showrepl only on the MIS(root DC), not on the
>> other
>> 2 DCs.
>> Thanks for help.
>> The repadmin / showrepl output is as
>>
>> repadmin running command /showrepl against server localhost
>>
>> Default-First-Site-Name\MIS
>>
>> DC Options: IS_GC
>> Site Options: (none)
>> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
>> DC invocationID: 79a17049-d367-4f70-a060-9c199120ac3e
>> ==== INBOUND NEIGHBORS ======================================
>>
>> DC=MyCom,DC=com
>>
>> Default-First-Site-Name\SUN via RPC
>>
>> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
>> Last attempt @ 2010-01-19 15:58:44 was successful.
>> CN=Configuration,DC=MyCom,DC=com
>>
>> Default-First-Site-Name\M00S via RPC
>> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
>> Last attempt @ 2010-01-19 15:55:11 failed, result 1753
>> (0x6d9):
>> There are no more endpoints available from the endpoint
>> mapper
>>
>> 33140 consecutive failure(s).
>> Last success @ 1983-06-18 18:17:20.
>> Default-First-Site-Name\V00S via RPC
>>
>> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
>> Last attempt @ 2010-01-19 15:55:11 was delayed for a normal
>> reason,
>> result 8418 (0x20e2):
>> The replication operation failed because of a schema mismatch
>> between the servers involved."
>>
>> Last success @ 2010-01-19 10:55:12.
>>
>> Default-First-Site-Name\SUN via RPC
>>
>> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
>> Last attempt @ 2010-01-19 16:00:52 was successful.
>> CN=Schema,CN=Configuration,DC=MyCom,DC=com
>>
>> Default-First-Site-Name\V00S via RPC
>> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
>> Last attempt @ 2010-01-19 15:55:11 was successful.
>> Default-First-Site-Name\M00S via RPC
>> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
>> Last attempt @ 2010-01-19 15:55:11 failed, result 1753
>> (0x6d9):
>> There are no more endpoints available from the endpoint
>> mapper
>>
>> 15943 consecutive failure(s).
>>
>> Last success @ 1983-06-18 17:47:59.
>>
>> Default-First-Site-Name\SUN via RPC
>> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
>> Last attempt @ 2010-01-19 15:55:11 was successful.
>> DC=m00domain,DC=MyCom,DC=com
>>
>> Default-First-Site-Name\M00S via RPC
>> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
>> Last attempt @ 2010-01-19 15:55:11 failed, result 1256
>> (0x4e8):
>> The remote system is not available. For information about
>> network troubleshooting, see Windows Help.
>>
>> 18255 consecutive failure(s).
>> Last success @ 1983-06-18 17:52:27.
>> DC=V00Domain,DC=MyCom,DC=com
>>
>> Default-First-Site-Name\V00S via RPC
>>
>> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
>>
>> Last attempt @ 2010-01-19 15:55:11 was delayed for a normal
>> reason, result 8418 (0x20e2):
>>
>> The replication operation failed because of a schema mismatch
>> between the servers involved."
>>
>> Last success @ 2010-01-19 10:55:12.
>>
>> Source: Default-First-Site-Name\M00S
>>
>> ******* 33140 CONSECUTIVE FAILURES since 1983-06-18 18:17:20
>>
>> Last error: 1256 (0x4e8):
>>
>> The remote system is not available. For information about
>> network troubleshooting, see Windows Help.
>>
>> "Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de>
>> ???????:6cb2911dc7df8cc66f74083d8b8@msnews.microsoft.com...
>>
>>> Hello Jason,
>>>
>>> Is this a follow up from "Default-First-Site-Name / Servers and DNS
>>> question" on 11.Jan.2010?
>>>
>>> As you said in the previous posting that server was a DC already
>>> before, did you ever removed it complete from the AD database before
>>> promoting again?
>>>
>>> Please post an unedited ipconfig /all from all 3 DCs and also the
>>> repadmin /showrepl from each one.
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers no rights.
>>> ** Please do NOT email, only reply to Newsgroups
>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> Hi,
>>>>
>>>> I Just promoted a member server to our AD as the 2nd DC(
>>>> IP:192.168.1.15) The new DC's LAN setting is as
>>>>
>>>> IP 192.168.1.15/255.255.0.0
>>>> DNS:192.168.1.1
>>>> The IP 192.168.1.1 is the 1st DC in our domain Mycom.com.
>>>> The 1st and 2nd DC are Windows 2003 Server and Windows 2003 Server
>>>> R2
>>>> respectively.
>>>> However, there's no DNS Server ruuning on the 2nd DC, I'm wondering
>>>> if
>>>> the
>>>> is normal or not.
>>>> Also, the 2nd DC's windows firewall is currently OFF, is this safe
>>>> enough
>>>> for a DC?
>>>> I looked up the event viewer of the 2nd DC and found a NTDS
>>>> Replication
>>>> error 1864 with user NT AUTHORITY\ANONYMOUS LOGON.
>>>> When I added an new user from the 1st DC for my domain, the new
>>>> created
>>>> account doesn't show up on the 2nd DC user list.
>>>> How do I fix these questions?
>>>> Thanks for help.
>>>> Jason
>
>
Re: New DC problem with event log NTDS Replication error 1864 [message #372392 is a reply to message #372278] Tue, 19 January 2010 21:56 Go to previous messageGo to next message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Jason Huang" <JasonHuang8888@hotmail.com> wrote in message
news:O3%23YxPXmKHA.4872@TK2MSFTNGP05.phx.gbl...
> Thanks.
> The output for the ipconfig of these 3 DC( mis, Sun, V00s) are
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : mis
> Primary Dns Suffix . . . . . . . : MyCom.com
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : Yes
> DNS Suffix Search List. . . . . . : MyCom.com
> com
>
> Ethernet adapter ????:
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : Intel(R) PRO/10 MT Network
> Connection
> Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.1
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . : 192.168.0.51
> DNS Servers . . . . . . . . . . . : 192.168.1.1
> Primary WINS Server . . . . . . . : 192.168.0.200
>
>
> Windows IP Configuration
>
>
> Host Name . . . . . . . . . . . . : Sun
> Primary Dns Suffix . . . . . . . : MyCom.com
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : MyCom.com
> com
>
>
> Ethernet adapter ???? 2:
>
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/10 EB Network
> Connection with I/O Acceleration #2
>
> Physical Address. . . . . . . . . : **-**-**-**-**-**
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.15
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . : 192.168.0.51
> DNS Servers . . . . . . . . . . . : 192.168.1.1
> Primary WINS Server . . . . . . . : 192.168.0.200
>
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : v00s
> Primary Dns Suffix . . . . . . . : V00Domain.MyCom.com
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : V00Domain.MyCom.com
> MyCom.com
> com
>
> Ethernet adapter ????:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/10 CT Network
> Connection
> Physical Address. . . . . . . . . : yy-yy-yy-yy-yy-yy
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.25.253
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . : 192.168.0.51
> DNS Servers . . . . . . . . . . . : 192.168.1.1
> Primary WINS Server . . . . . . . : 192.168.0.200
>
>

Hi Jason,

Curious:

What is IP 192.168.0.200? It's the WINS server specified on the three DCs.
Is there another DC?

I see that 192.168.1.1 is the only DNS server. If you look in the MyCom.com,
are SUN and MIS both registered in the zone

How about v00s? That appears to be a DC in a child domain called
V00Domain.MyCom.com. So you have two domains in the forest. Since it's using
192.168.1.1 (MIS) for DNS, is there a child zone under MyCom.com called
V00Domain?

Do the SRV records exist for both domains?

Which DCs are Global Catalogs?

Keep in mind, in a multi-domain forest, it is required to have a minimum of
two DCs in each domain. This is because the Infrastructure Master FSMO role
cannot be on a GC, so you would have one DC to be a GC, and the other hold
the Infrastructure Master role. I assume V00s is not a Global Catalog?

Curious why the large subnet mask? A class B subnet mask (255.255.0.0)
encompasses 65,534 IP addresses. I assume this is a large infractructure?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please
contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.
Re: New DC problem with event log NTDS Replication error 1864 [message #372427 is a reply to message #372392] Tue, 19 January 2010 23:18 Go to previous messageGo to next message
Jason Huang  is currently offline Jason Huang  Taiwan
Messages: 60
Registered: September 2009
Member
Hi,

The IP 192.168.0.200 is the WINS Server's IP, which is a stand alone Win2003
server, not a domain member yet.
The v00s is a child zone DC for V00Domain.MyCom.com, and there're totally 3
DC (MIS, Sun, v00s).
Under the MIS(192.168.1.1) DNS, the MIS and Sun are both registered in the
zone.
The MyCom.com has MIS and Sun srv, while the V00Domain.MyCom.com has v00s
srv.
How do I determine which DC is the Global Catalog?

Thanks for help.


Jason

>
> Hi Jason,
>
> Curious:
>
> What is IP 192.168.0.200? It's the WINS server specified on the three DCs.
> Is there another DC?
>
> I see that 192.168.1.1 is the only DNS server. If you look in the
> MyCom.com, are SUN and MIS both registered in the zone
>
> How about v00s? That appears to be a DC in a child domain called
> V00Domain.MyCom.com. So you have two domains in the forest. Since it's
> using 192.168.1.1 (MIS) for DNS, is there a child zone under MyCom.com
> called V00Domain?
>
> Do the SRV records exist for both domains?
>
> Which DCs are Global Catalogs?
>
> Keep in mind, in a multi-domain forest, it is required to have a minimum
> of two DCs in each domain. This is because the Infrastructure Master FSMO
> role cannot be on a GC, so you would have one DC to be a GC, and the other
> hold the Infrastructure Master role. I assume V00s is not a Global
> Catalog?
>
> Curious why the large subnet mask? A class B subnet mask (255.255.0.0)
> encompasses 65,534 IP addresses. I assume this is a large infractructure?
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
> MCSA 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
> Microsoft MVP - Directory Services
>
> If you feel this is an urgent issue and require immediate assistance,
> please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>
>
>
>
>
>
>
>
Re: New DC problem with event log NTDS Replication error 1864 [message #372450 is a reply to message #372427] Wed, 20 January 2010 00:08 Go to previous messageGo to next message
meiweb  is currently offline meiweb  Germany
Messages: 2225
Registered: September 2009
Senior Member
Hello Jason,

On "mis" disable the WINS proxy.

Please post the repadmin command from all 3 DCs.

In AD sites and services expand the sitename, if not changed, "default first
site name",servers, DC name down to NTDS settings and open the properties
of NTDS settings, here you see the checkmark for GC.

Additional post the requested outputs from Paul.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi,
>
> The IP 192.168.0.200 is the WINS Server's IP, which is a stand alone
> Win2003
> server, not a domain member yet.
> The v00s is a child zone DC for V00Domain.MyCom.com, and there're
> totally 3
> DC (MIS, Sun, v00s).
> Under the MIS(192.168.1.1) DNS, the MIS and Sun are both registered in
> the
> zone.
> The MyCom.com has MIS and Sun srv, while the V00Domain.MyCom.com has
> v00s
> srv.
> How do I determine which DC is the Global Catalog?
> Thanks for help.
>
> Jason
>
>> Hi Jason,
>>
>> Curious:
>>
>> What is IP 192.168.0.200? It's the WINS server specified on the three
>> DCs. Is there another DC?
>>
>> I see that 192.168.1.1 is the only DNS server. If you look in the
>> MyCom.com, are SUN and MIS both registered in the zone
>>
>> How about v00s? That appears to be a DC in a child domain called
>> V00Domain.MyCom.com. So you have two domains in the forest. Since
>> it's using 192.168.1.1 (MIS) for DNS, is there a child zone under
>> MyCom.com called V00Domain?
>>
>> Do the SRV records exist for both domains?
>>
>> Which DCs are Global Catalogs?
>>
>> Keep in mind, in a multi-domain forest, it is required to have a
>> minimum of two DCs in each domain. This is because the Infrastructure
>> Master FSMO role cannot be on a GC, so you would have one DC to be a
>> GC, and the other hold the Infrastructure Master role. I assume V00s
>> is not a Global Catalog?
>>
>> Curious why the large subnet mask? A class B subnet mask
>> (255.255.0.0) encompasses 65,534 IP addresses. I assume this is a
>> large infractructure?
>>
>> -- Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.
>>
>> Please reply back to the newsgroup or forum for collaboration benefit
>> among responding engineers, and to help others benefit from your
>> resolution.
>>
>> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007,
>> MCSE &
>> MCSA 2003/2000, MCSA Messaging 2003
>> Microsoft Certified Trainer
>> Microsoft MVP - Directory Services
>> If you feel this is an urgent issue and require immediate assistance,
>> please contact Microsoft PSS directly. Please check
>> http://support.microsoft.com for regional support phone numbers.
>>
Re: New DC problem with event log NTDS Replication error 1864 [message #372486 is a reply to message #372450] Wed, 20 January 2010 02:18 Go to previous messageGo to next message
Jason Huang  is currently offline Jason Huang  Taiwan
Messages: 60
Registered: September 2009
Member
The GC is the DC MIS(192.168.1.1), and the WINS proxy is set to No.

MIS:


repadmin running command /showrepl against server localhost

Default-First-Site-Name\MIS
DC Options: IS_GC
Site Options: (none)
DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
DC invocationID: 79a17049-d367-4f70-a060-9c199120ac3e

==== INBOUND NEIGHBORS ======================================

DC=MyCom,DC=com
Default-First-Site-Name\SUN via RPC
DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-20 17:03:14 was successful.

CN=Configuration,DC=MyCom,DC=com
Default-First-Site-Name\M00S via RPC
DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
Last attempt @ 2010-01-20 16:55:08 failed, result 1753 (0x6d9):
There are no more endpoints available from the endpoint mapper
33165 consecutive failure(s).
Last success @ 1983-06-18 18:17:20.
Default-First-Site-Name\V00S via RPC
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-20 16:55:08 was delayed for a normal reason,
result 8418 (0x20e2):
The replication operation failed because of a schema mismatch between
the servers involved

Last success @ 2010-01-19 10:55:12.
Default-First-Site-Name\SUN via RPC
DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-20 16:55:08 was successful.



CN=Schema,CN=Configuration,DC=MyCom,DC=com
Default-First-Site-Name\V00S via RPC
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-20 16:55:08 was successful.
Default-First-Site-Name\M00S via RPC
DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
Last attempt @ 2010-01-20 16:55:08 failed, result 1753 (0x6d9):
There are no more endpoints available from the endpoint mapper

15968 consecutive failure(s).
Last success @ 1983-06-18 17:47:59.
Default-First-Site-Name\SUN via RPC

DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-20 16:55:08 was successful.


DC=m00domain,DC=MyCom,DC=com
Default-First-Site-Name\M00S via RPC
DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
Last attempt @ 2010-01-20 16:55:08 failed, result 1256 (0x4e8):
The remote system is not available. For information about
network troubleshooting, see Windows Help.

18280 consecutive failure(s).
Last success @ 1983-06-18 17:52:27.


DC=V00Domain,DC=MyCom,DC=com
Default-First-Site-Name\V00S via RPC
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-20 16:55:08 was delayed for a normal reason,
result 8418 (0x20e2):

The replication operation failed because of a schema mismatch between
the servers involved

Last success @ 2010-01-19 10:55:12.

Source: Default-First-Site-Name\M00S

******* 33165 CONSECUTIVE FAILURES since 1983-06-18 18:17:20

Last error: 1256 (0x4e8):

The remote system is not available. For information about
network troubleshooting, see Windows Help.


SUN:


repadmin running command /showrepl against server localhost



Default-First-Site-Name\SUN
DC Options: (none)
Site Options: (none)
DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
DC invocationID: 33b94c6f-8a5a-4ad5-9890-cb2336edb937


==== INBOUND NEIGHBORS ======================================



DC=MyCom,DC=com

Default-First-Site-Name\MIS via RPC

DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
Last attempt @ 2010-01-20 17:12:22 was successful.


CN=Configuration,DC=MyCom,DC=com
Default-First-Site-Name\MIS via RPC
DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
Last attempt @ 2010-01-20 16:49:14 was successful.


CN=Schema,CN=Configuration,DC=MyCom,DC=com

Default-First-Site-Name\MIS via RPC
DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
Last attempt @ 2010-01-20 16:49:14 was successful.
Default-First-Site-Name\V00S via RPC
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-20 16:49:14 was successful.



Source: Default-First-Site-Name\V00S

******* 1 CONSECUTIVE FAILURES since 2010-01-20 17:09:15

Last error: 8418 (0x20e2):
The replication operation failed because of a schema mismatch
between
the servers involved


Naming Context: CN=Configuration,DC=MyCom,DC=com
Source: Default-First-Site-Name\V00S

******* WARNING: KCC could not add this REPLICA LINK due to error.

Source: Default-First-Site-Name\M00S

******* 56 CONSECUTIVE FAILURES since 2010-01-20 03:24:10

Last error: 1753 (0x6d9):
There are no more endpoints available from the endpoint mapper


Naming Context: CN=Schema,CN=Configuration,DC=MyCom,DC=com
Source: Default-First-Site-Name\M00S

******* WARNING: KCC could not add this REPLICA LINK due to error.


Naming Context: CN=Configuration,DC=MyCom,DC=com
Source: Default-First-Site-Name\M00S

******* WARNING: KCC could not add this REPLICA LINK due to error.




V00S:
repadmin running command /showrepl against server localhost

Default-First-Site-Name\V00S
DC Options: (none)
Site Options: (none)
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
DC invocationID: 69bbf530-7664-4463-90d0-718a1e676213


==== INBOUND NEIGHBORS ======================================


CN=Configuration,DC=MyCom,DC=com
Default-First-Site-Name\M00S via RPC
DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
Last attempt @ 2010-01-20 08:59:52 failed, result 1753 (0x6d9):
There are no more endpoints available from the endpoint maper
100930 consecutive failure(s).
Last success @ 2005-04-25 16:26:28.
Default-First-Site-Name\MIS via RPC
DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
Last attempt @ 2010-01-20 09:15:38 failed, result 8614 (0x21a6):
The Active Directory cannot replicate with this server because the time
since the last replication with this server has exceeded the tombstone
lifetime.

39408 consecutive failure(s).

Last success @ 2005-04-26 13:49:25.

CN=Schema,CN=Configuration,DC=MyCom,DC=com
Default-First-Site-Name\M00S via RPC
DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
Last attempt @ 2010-01-20 08:59:52 failed, result 1753 (0x6d9):
There are no more endpoints available from the endpoint mapper
39347 consecutive failure(s).
Last success @ 2005-04-25 15:54:14.
Default-First-Site-Name\MIS via RPC
DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
Last attempt @ 2010-01-20 08:59:52 failed, result 8614 (0x21a6):


The Active Directory cannot replicate with this server because the time
since the last replication with this server has exceeded the tombstone
lifetime.
39341 consecutive failure(s).
Last success @ 2005-04-26 12:53:57.


Source: Default-First-Site-Name\M00S

******* 100930 CONSECUTIVE FAILURES since 2005-04-25 16:26:28

Last error: 1753 (0x6d9):
There are no more endpoints available from the endpoint mapper


Source: Default-First-Site-Name\MIS
******* 39408 CONSECUTIVE FAILURES since 2005-04-26 13:49:25
Last error: 8614 (0x21a6):
The Active Directory cannot replicate with this server because the time
since the last replication with this server has exceeded the tombstone
lifetime.
Re: New DC problem with event log NTDS Replication error 1864 [message #372543 is a reply to message #372486] Wed, 20 January 2010 04:25 Go to previous messageGo to next message
meiweb  is currently offline meiweb  Germany
Messages: 2225
Registered: September 2009
Senior Member
Hello Jason,

What it M00S for a machine? Is that one removed from the domain some time
ago? Check with the following article the AD database and cleanup old DCs
from the domain:
http://support.microsoft.com/kb/555846/en-us

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> The GC is the DC MIS(192.168.1.1), and the WINS proxy is set to No.
>
> MIS:
>
> repadmin running command /showrepl against server localhost
>
> Default-First-Site-Name\MIS
> DC Options: IS_GC
> Site Options: (none)
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
> DC invocationID: 79a17049-d367-4f70-a060-9c199120ac3e
> ==== INBOUND NEIGHBORS ======================================
>
> DC=MyCom,DC=com
> Default-First-Site-Name\SUN via RPC
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> Last attempt @ 2010-01-20 17:03:14 was successful.
> CN=Configuration,DC=MyCom,DC=com
> Default-First-Site-Name\M00S via RPC
> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
> Last attempt @ 2010-01-20 16:55:08 failed, result 1753
> (0x6d9):
> There are no more endpoints available from the endpoint
> mapper
> 33165 consecutive failure(s).
> Last success @ 1983-06-18 18:17:20.
> Default-First-Site-Name\V00S via RPC
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> Last attempt @ 2010-01-20 16:55:08 was delayed for a normal
> reason,
> result 8418 (0x20e2):
> The replication operation failed because of a schema mismatch
> between
> the servers involved
> Last success @ 2010-01-19 10:55:12.
> Default-First-Site-Name\SUN via RPC
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> Last attempt @ 2010-01-20 16:55:08 was successful.
> CN=Schema,CN=Configuration,DC=MyCom,DC=com
> Default-First-Site-Name\V00S via RPC
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> Last attempt @ 2010-01-20 16:55:08 was successful.
> Default-First-Site-Name\M00S via RPC
> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
> Last attempt @ 2010-01-20 16:55:08 failed, result 1753
> (0x6d9):
> There are no more endpoints available from the endpoint
> mapper
> 15968 consecutive failure(s).
> Last success @ 1983-06-18 17:47:59.
> Default-First-Site-Name\SUN via RPC
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> Last attempt @ 2010-01-20 16:55:08 was successful.
> DC=m00domain,DC=MyCom,DC=com
> Default-First-Site-Name\M00S via RPC
> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
> Last attempt @ 2010-01-20 16:55:08 failed, result 1256
> (0x4e8):
> The remote system is not available. For information about
> network troubleshooting, see Windows Help.
> 18280 consecutive failure(s).
> Last success @ 1983-06-18 17:52:27.
> DC=V00Domain,DC=MyCom,DC=com
> Default-First-Site-Name\V00S via RPC
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> Last attempt @ 2010-01-20 16:55:08 was delayed for a normal
> reason,
> result 8418 (0x20e2):
> The replication operation failed because of a schema mismatch
> between the servers involved
>
> Last success @ 2010-01-19 10:55:12.
>
> Source: Default-First-Site-Name\M00S
>
> ******* 33165 CONSECUTIVE FAILURES since 1983-06-18 18:17:20
>
> Last error: 1256 (0x4e8):
>
> The remote system is not available. For information
> about network troubleshooting, see Windows Help.
>
> SUN:
>
> repadmin running command /showrepl against server localhost
>
> Default-First-Site-Name\SUN
> DC Options: (none)
> Site Options: (none)
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> DC invocationID: 33b94c6f-8a5a-4ad5-9890-cb2336edb937
> ==== INBOUND NEIGHBORS ======================================
>
> DC=MyCom,DC=com
>
> Default-First-Site-Name\MIS via RPC
>
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
> Last attempt @ 2010-01-20 17:12:22 was successful.
> CN=Configuration,DC=MyCom,DC=com
> Default-First-Site-Name\MIS via RPC
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
> Last attempt @ 2010-01-20 16:49:14 was successful.
> CN=Schema,CN=Configuration,DC=MyCom,DC=com
>
> Default-First-Site-Name\MIS via RPC
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
> Last attempt @ 2010-01-20 16:49:14 was successful.
> Default-First-Site-Name\V00S via RPC
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> Last attempt @ 2010-01-20 16:49:14 was successful.
> Source: Default-First-Site-Name\V00S
>
> ******* 1 CONSECUTIVE FAILURES since 2010-01-20 17:09:15
>
> Last error: 8418 (0x20e2):
> The replication operation failed because of a schema
> mismatch
> between
> the servers involved
>
> Naming Context: CN=Configuration,DC=MyCom,DC=com
> Source: Default-First-Site-Name\V00S
> ******* WARNING: KCC could not add this REPLICA LINK due to error.
>
> Source: Default-First-Site-Name\M00S
>
> ******* 56 CONSECUTIVE FAILURES since 2010-01-20 03:24:10
>
> Last error: 1753 (0x6d9):
> There are no more endpoints available from the endpoint
> mapper
> Naming Context: CN=Schema,CN=Configuration,DC=MyCom,DC=com Source:
> Default-First-Site-Name\M00S
>
> ******* WARNING: KCC could not add this REPLICA LINK due to error.
>
> Naming Context: CN=Configuration,DC=MyCom,DC=com
> Source: Default-First-Site-Name\M00S
> ******* WARNING: KCC could not add this REPLICA LINK due to error.
>
> V00S:
> repadmin running command /showrepl against server localhost
> Default-First-Site-Name\V00S
> DC Options: (none)
> Site Options: (none)
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> DC invocationID: 69bbf530-7664-4463-90d0-718a1e676213
> ==== INBOUND NEIGHBORS ======================================
>
> CN=Configuration,DC=MyCom,DC=com
> Default-First-Site-Name\M00S via RPC
> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
> Last attempt @ 2010-01-20 08:59:52 failed, result 1753
> (0x6d9):
> There are no more endpoints available from the endpoint
> maper
> 100930 consecutive failure(s).
> Last success @ 2005-04-25 16:26:28.
> Default-First-Site-Name\MIS via RPC
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
> Last attempt @ 2010-01-20 09:15:38 failed, result 8614
> (0x21a6):
> The Active Directory cannot replicate with this server because the
> time
> since the last replication with this server has exceeded the tombstone
> lifetime.
>
> 39408 consecutive failure(s).
>
> Last success @ 2005-04-26 13:49:25.
>
> CN=Schema,CN=Configuration,DC=MyCom,DC=com
> Default-First-Site-Name\M00S via RPC
> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
> Last attempt @ 2010-01-20 08:59:52 failed, result 1753
> (0x6d9):
> There are no more endpoints available from the endpoint
> mapper
> 39347 consecutive failure(s).
> Last success @ 2005-04-25 15:54:14.
> Default-First-Site-Name\MIS via RPC
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
> Last attempt @ 2010-01-20 08:59:52 failed, result 8614
> (0x21a6):
> The Active Directory cannot replicate with this server because the
> time
> since the last replication with this server has exceeded the tombstone
> lifetime.
> 39341 consecutive failure(s).
> Last success @ 2005-04-26 12:53:57.
> Source: Default-First-Site-Name\M00S
>
> ******* 100930 CONSECUTIVE FAILURES since 2005-04-25 16:26:28
>
> Last error: 1753 (0x6d9):
> There are no more endpoints available from the endpoint
> mapper
> Source: Default-First-Site-Name\MIS
> ******* 39408 CONSECUTIVE FAILURES since 2005-04-26 13:49:25
> Last error: 8614 (0x21a6):
> The Active Directory cannot replicate with this server because the
> time
> since the last replication with this server has exceeded the tombstone
> lifetime.
>
Re: New DC problem with event log NTDS Replication error 1864 [message #372595 is a reply to message #372486] Wed, 20 January 2010 06:10 Go to previous messageGo to next message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Jason Huang" <JasonHuang8888@hotmail.com> wrote in message
news:uzvj8FbmKHA.5520@TK2MSFTNGP06.phx.gbl...
> The GC is the DC MIS(192.168.1.1), and the WINS proxy is set to No.
>
> MIS:
>
>
> repadmin running command /showrepl against server localhost
>
> Default-First-Site-Name\MIS
> DC Options: IS_GC
> Site Options: (none)
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
> DC invocationID: 79a17049-d367-4f70-a060-9c199120ac3e
>
> ==== INBOUND NEIGHBORS ======================================
>
> DC=MyCom,DC=com
> Default-First-Site-Name\SUN via RPC
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> Last attempt @ 2010-01-20 17:03:14 was successful.
>
> CN=Configuration,DC=MyCom,DC=com
> Default-First-Site-Name\M00S via RPC
> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
> Last attempt @ 2010-01-20 16:55:08 failed, result 1753 (0x6d9):
> There are no more endpoints available from the endpoint mapper
> 33165 consecutive failure(s).
> Last success @ 1983-06-18 18:17:20.
> Default-First-Site-Name\V00S via RPC
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> Last attempt @ 2010-01-20 16:55:08 was delayed for a normal reason,
> result 8418 (0x20e2):
> The replication operation failed because of a schema mismatch between
> the servers involved
>
> Last success @ 2010-01-19 10:55:12.
> Default-First-Site-Name\SUN via RPC
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> Last attempt @ 2010-01-20 16:55:08 was successful.
>
>
>
> CN=Schema,CN=Configuration,DC=MyCom,DC=com
> Default-First-Site-Name\V00S via RPC
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> Last attempt @ 2010-01-20 16:55:08 was successful.
> Default-First-Site-Name\M00S via RPC
> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
> Last attempt @ 2010-01-20 16:55:08 failed, result 1753 (0x6d9):
> There are no more endpoints available from the endpoint mapper
>
> 15968 consecutive failure(s).
> Last success @ 1983-06-18 17:47:59.
> Default-First-Site-Name\SUN via RPC
>
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> Last attempt @ 2010-01-20 16:55:08 was successful.
>
>
> DC=m00domain,DC=MyCom,DC=com
> Default-First-Site-Name\M00S via RPC
> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
> Last attempt @ 2010-01-20 16:55:08 failed, result 1256 (0x4e8):
> The remote system is not available. For information about
> network troubleshooting, see Windows Help.
>
> 18280 consecutive failure(s).
> Last success @ 1983-06-18 17:52:27.
>
>
> DC=V00Domain,DC=MyCom,DC=com
> Default-First-Site-Name\V00S via RPC
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> Last attempt @ 2010-01-20 16:55:08 was delayed for a normal reason,
> result 8418 (0x20e2):
>
> The replication operation failed because of a schema mismatch between
> the servers involved
>
> Last success @ 2010-01-19 10:55:12.
>
> Source: Default-First-Site-Name\M00S
>
> ******* 33165 CONSECUTIVE FAILURES since 1983-06-18 18:17:20
>
> Last error: 1256 (0x4e8):
>
> The remote system is not available. For information about
> network troubleshooting, see Windows Help.
>
>
> SUN:
>
>
> repadmin running command /showrepl against server localhost
>
>
>
> Default-First-Site-Name\SUN
> DC Options: (none)
> Site Options: (none)
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> DC invocationID: 33b94c6f-8a5a-4ad5-9890-cb2336edb937
>
>
> ==== INBOUND NEIGHBORS ======================================
>
>
>
> DC=MyCom,DC=com
>
> Default-First-Site-Name\MIS via RPC
>
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
> Last attempt @ 2010-01-20 17:12:22 was successful.
>
>
> CN=Configuration,DC=MyCom,DC=com
> Default-First-Site-Name\MIS via RPC
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
> Last attempt @ 2010-01-20 16:49:14 was successful.
>
>
> CN=Schema,CN=Configuration,DC=MyCom,DC=com
>
> Default-First-Site-Name\MIS via RPC
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
> Last attempt @ 2010-01-20 16:49:14 was successful.
> Default-First-Site-Name\V00S via RPC
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> Last attempt @ 2010-01-20 16:49:14 was successful.
>
>
>
> Source: Default-First-Site-Name\V00S
>
> ******* 1 CONSECUTIVE FAILURES since 2010-01-20 17:09:15
>
> Last error: 8418 (0x20e2):
> The replication operation failed because of a schema mismatch
> between
> the servers involved
>
>
> Naming Context: CN=Configuration,DC=MyCom,DC=com
> Source: Default-First-Site-Name\V00S
>
> ******* WARNING: KCC could not add this REPLICA LINK due to error.
>
> Source: Default-First-Site-Name\M00S
>
> ******* 56 CONSECUTIVE FAILURES since 2010-01-20 03:24:10
>
> Last error: 1753 (0x6d9):
> There are no more endpoints available from the endpoint mapper
>
>
> Naming Context: CN=Schema,CN=Configuration,DC=MyCom,DC=com
> Source: Default-First-Site-Name\M00S
>
> ******* WARNING: KCC could not add this REPLICA LINK due to error.
>
>
> Naming Context: CN=Configuration,DC=MyCom,DC=com
> Source: Default-First-Site-Name\M00S
>
> ******* WARNING: KCC could not add this REPLICA LINK due to error.
>
>
>
>
> V00S:
> repadmin running command /showrepl against server localhost
>
> Default-First-Site-Name\V00S
> DC Options: (none)
> Site Options: (none)
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> DC invocationID: 69bbf530-7664-4463-90d0-718a1e676213
>
>
> ==== INBOUND NEIGHBORS ======================================
>
>
> CN=Configuration,DC=MyCom,DC=com
> Default-First-Site-Name\M00S via RPC
> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
> Last attempt @ 2010-01-20 08:59:52 failed, result 1753 (0x6d9):
> There are no more endpoints available from the endpoint maper
> 100930 consecutive failure(s).
> Last success @ 2005-04-25 16:26:28.
> Default-First-Site-Name\MIS via RPC
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
> Last attempt @ 2010-01-20 09:15:38 failed, result 8614 (0x21a6):
> The Active Directory cannot replicate with this server because the time
> since the last replication with this server has exceeded the tombstone
> lifetime.
>
> 39408 consecutive failure(s).
>
> Last success @ 2005-04-26 13:49:25.
>
> CN=Schema,CN=Configuration,DC=MyCom,DC=com
> Default-First-Site-Name\M00S via RPC
> DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
> Last attempt @ 2010-01-20 08:59:52 failed, result 1753 (0x6d9):
> There are no more endpoints available from the endpoint mapper
> 39347 consecutive failure(s).
> Last success @ 2005-04-25 15:54:14.
> Default-First-Site-Name\MIS via RPC
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
> Last attempt @ 2010-01-20 08:59:52 failed, result 8614 (0x21a6):
>
>
> The Active Directory cannot replicate with this server because the time
> since the last replication with this server has exceeded the tombstone
> lifetime.
> 39341 consecutive failure(s).
> Last success @ 2005-04-26 12:53:57.
>
>
> Source: Default-First-Site-Name\M00S
>
> ******* 100930 CONSECUTIVE FAILURES since 2005-04-25 16:26:28
>
> Last error: 1753 (0x6d9):
> There are no more endpoints available from the endpoint mapper
>
>
> Source: Default-First-Site-Name\MIS
> ******* 39408 CONSECUTIVE FAILURES since 2005-04-26 13:49:25
> Last error: 8614 (0x21a6):
> The Active Directory cannot replicate with this server because the time
> since the last replication with this server has exceeded the tombstone
> lifetime.
>
>
>
>



As Meinolf indicated, M00S has to be removed from the AD database.

I also suggest to promote another DC into the v00s.mycom.com domain, and
make it a GC.

Ace
Re: New DC problem with event log NTDS Replication error 1864 [message #373546 is a reply to message #372543] Thu, 21 January 2010 01:55 Go to previous messageGo to next message
Jason Huang  is currently offline Jason Huang  Taiwan
Messages: 60
Registered: September 2009
Member
The M00S is a Win2003 stand alone server, it was domoted long time ago.
Thanks for your guys' help, I just deleted and cleaned the m00domain few
minutes ago.
It still has the result 8418 (0x20e2):

The replication operation failed because of a schema mismatch between
the servers involved.






repadmin running command /showrepl against server localhost


Default-First-Site-Name\MIS
DC Options: IS_GC
Site Options: (none)

DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
DC invocationID: 79a17049-d367-4f70-a060-9c199120ac3e


==== INBOUND NEIGHBORS ======================================


DC=etc,DC=org,DC=tw

Default-First-Site-Name\SUN via RPC
DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-21 16:41:35 was successful.

CN=Configuration,DC=MyCom,DC=com
Default-First-Site-Name\V00S via RPC
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-21 16:41:28 was delayed for a normal reason,
result 8418 (0x20e2):

The replication operation failed because of a schema mismatch between
the servers involved.

Last success @ 2010-01-19 10:55:12.
Default-First-Site-Name\SUN via RPC
DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-21 16:45:51 was successful.


CN=Schema,CN=Configuration,DC=MyCom,DC=com

Default-First-Site-Name\V00S via RPC
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-21 15:55:08 was successful.
Default-First-Site-Name\ETCSUN via RPC
DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-21 15:55:08 was successful.


DC=V00Domain,DC=MyCom,DC=com
Default-First-Site-Name\V00S via RPC

DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-21 16:42:02 was delayed for a normal reason,
result 8418 (0x20e2):

The replication operation failed because of a schema mismatch between
the servers involved.

Last success @ 2010-01-19 10:55:12.
Re: New DC problem with event log NTDS Replication error 1864 [message #373552 is a reply to message #373546] Thu, 21 January 2010 02:04 Go to previous messageGo to next message
meiweb  is currently offline meiweb  Germany
Messages: 2225
Registered: September 2009
Senior Member
Hello Jason,

Please check the following article:
http://support.microsoft.com/kb/825782

http://support.microsoft.com/kb/307323

Are all DCs using SP2 and the latest available patches?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> The M00S is a Win2003 stand alone server, it was domoted long time
> ago.
> Thanks for your guys' help, I just deleted and cleaned the m00domain
> few
> minutes ago.
> It still has the result 8418 (0x20e2):
> The replication operation failed because of a schema mismatch
> between the servers involved.
>
> repadmin running command /showrepl against server localhost
>
> Default-First-Site-Name\MIS
> DC Options: IS_GC
> Site Options: (none)
> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e DC invocationID:
> 79a17049-d367-4f70-a060-9c199120ac3e
>
> ==== INBOUND NEIGHBORS ======================================
>
> DC=etc,DC=org,DC=tw
>
> Default-First-Site-Name\SUN via RPC
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> Last attempt @ 2010-01-21 16:41:35 was successful.
> CN=Configuration,DC=MyCom,DC=com
> Default-First-Site-Name\V00S via RPC
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> Last attempt @ 2010-01-21 16:41:28 was delayed for a normal
> reason,
> result 8418 (0x20e2):
> The replication operation failed because of a schema mismatch
> between the servers involved.
>
> Last success @ 2010-01-19 10:55:12.
> Default-First-Site-Name\SUN via RPC
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> Last attempt @ 2010-01-21 16:45:51 was successful.
> CN=Schema,CN=Configuration,DC=MyCom,DC=com
>
> Default-First-Site-Name\V00S via RPC
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> Last attempt @ 2010-01-21 15:55:08 was successful.
> Default-First-Site-Name\ETCSUN via RPC
> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
> Last attempt @ 2010-01-21 15:55:08 was successful.
> DC=V00Domain,DC=MyCom,DC=com
> Default-First-Site-Name\V00S via RPC
> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
> Last attempt @ 2010-01-21 16:42:02 was delayed for a normal
> reason,
> result 8418 (0x20e2):
> The replication operation failed because of a schema mismatch
> between the servers involved.
>
> Last success @ 2010-01-19 10:55:12.
>
Re: New DC problem with event log NTDS Replication error 1864 [message #373660 is a reply to message #373552] Thu, 21 January 2010 06:17 Go to previous message
pbbergs  is currently offline pbbergs  United States
Messages: 1024
Registered: July 2009
Senior Member
You may also want to review below, this may assist as well.
http://support.microsoft.com/kb/838179

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
news:6cb2911dca108cc689833ea57c4@msnews.microsoft.com...
> Hello Jason,
>
> Please check the following article:
> http://support.microsoft.com/kb/825782
>
> http://support.microsoft.com/kb/307323
>
> Are all DCs using SP2 and the latest available patches?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> The M00S is a Win2003 stand alone server, it was domoted long time
>> ago.
>> Thanks for your guys' help, I just deleted and cleaned the m00domain
>> few
>> minutes ago.
>> It still has the result 8418 (0x20e2):
>> The replication operation failed because of a schema mismatch
>> between the servers involved.
>>
>> repadmin running command /showrepl against server localhost
>>
>> Default-First-Site-Name\MIS
>> DC Options: IS_GC
>> Site Options: (none)
>> DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e DC invocationID:
>> 79a17049-d367-4f70-a060-9c199120ac3e
>>
>> ==== INBOUND NEIGHBORS ======================================
>>
>> DC=etc,DC=org,DC=tw
>>
>> Default-First-Site-Name\SUN via RPC
>> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
>> Last attempt @ 2010-01-21 16:41:35 was successful.
>> CN=Configuration,DC=MyCom,DC=com
>> Default-First-Site-Name\V00S via RPC
>> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
>> Last attempt @ 2010-01-21 16:41:28 was delayed for a normal
>> reason,
>> result 8418 (0x20e2):
>> The replication operation failed because of a schema mismatch
>> between the servers involved.
>>
>> Last success @ 2010-01-19 10:55:12.
>> Default-First-Site-Name\SUN via RPC
>> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
>> Last attempt @ 2010-01-21 16:45:51 was successful.
>> CN=Schema,CN=Configuration,DC=MyCom,DC=com
>>
>> Default-First-Site-Name\V00S via RPC
>> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
>> Last attempt @ 2010-01-21 15:55:08 was successful.
>> Default-First-Site-Name\ETCSUN via RPC
>> DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
>> Last attempt @ 2010-01-21 15:55:08 was successful.
>> DC=V00Domain,DC=MyCom,DC=com
>> Default-First-Site-Name\V00S via RPC
>> DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
>> Last attempt @ 2010-01-21 16:42:02 was delayed for a normal
>> reason,
>> result 8418 (0x20e2):
>> The replication operation failed because of a schema mismatch
>> between the servers involved.
>>
>> Last success @ 2010-01-19 10:55:12.
>>
>
>
Previous Topic:How to Rename Active Directory
Next Topic:AD health check and cleanup
Goto Forum:
  


Current Time: Wed Jan 17 05:34:48 MST 2018

Total time taken to generate the page: 0.04205 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software