Sid_F
asked on
sysvol and PGO replicating or not
How can I verify if sysvol and GPO is replicating between domain controllers. I know they did replicate before as they were on the same site but since moving to another remote site I am not sure. I can see the dates on the sysvol folder are the same between the domain controllers. I am also curious as I know GPO's have been changed in the past few weeks yet the dates on the sysvol folder for policies have not. Its 2003 domain.,
ASKER
when I run showrepl, the output is broken down into a few different sections, on the first section it shows 3 replications for different guid numbers, the first one is successful the second one a minute before failed and the third was for about ten days ago failed.
other sections are similar but I am unsure of exactly what I am looking for
other sections are similar but I am unsure of exactly what I am looking for
can you paste it here?
right click and press mark then press enter then press paste in ee (redact sensitive information and possibly change domainnames to something else)
right click and press mark then press enter then press paste in ee (redact sensitive information and possibly change domainnames to something else)
ASKER
For security I can't paste sorry!
ASKER
ok details removed
Default-First-Site\mycompa ny-server1
DC Options: (none)
Site Options: (none)
DC object GUID: e969e570-9334-4cc3-aa80-79 fe94ecbd9f
DC invocationID: af1b471f-cd3d-4bad-b7a1-0f 93eb66b2f4
==== INBOUND NEIGHBORS ========================== ========== ==
DC=mycompany,DC=local
Default-First-Site\mycompa ny-server2 via RPC
DC object GUID: a6067ddb-5854-472d-b6ce-fe 30625083f9
Last attempt @ 2013-02-07 11:25:34 was successful.
Default-First-Site\mycompa ny-mainDC via RPC
DC object GUID: 1f5739a0-d579-4c20-97af-90 2d9fc50744
Last attempt @ 2013-02-07 11:26:17 failed, result 1722 (0x6ba):
The RPC server is unavailable.
51857 consecutive failure(s).
Last success @ 2013-01-20 00:20:17.
Default-First-Site\mycompa ny-secondD C via RPC
DC object GUID: 844e9cc0-41a9-49da-8449-05 23cf96aa36
Last attempt @ 2013-02-07 11:26:17 was successful.
CN=Configuration,DC=mycomp any,DC=loc al
Default-First-Site\mycompa ny-server2 via RPC
DC object GUID: a6067ddb-5854-472d-b6ce-fe 30625083f9
Last attempt @ 2013-02-07 10:57:05 was successful.
Default-First-Site\mycompa ny-secondD C via RPC
DC object GUID: 844e9cc0-41a9-49da-8449-05 23cf96aa36
Last attempt @ 2013-02-07 10:57:05 was successful.
Default-First-Site\mycompa ny-mainDC via RPC
DC object GUID: 1f5739a0-d579-4c20-97af-90 2d9fc50744
Last attempt @ 2013-02-07 10:57:26 failed, result 1722 (0x6ba):
The RPC server is unavailable.
458 consecutive failure(s).
Last success @ 2013-01-19 23:56:48.
CN=Schema,CN=Configuration ,DC=mycomp any,DC=loc al
Default-First-Site\mycompa ny-server2 via RPC
DC object GUID: a6067ddb-5854-472d-b6ce-fe 30625083f9
Last attempt @ 2013-02-07 10:57:26 was successful.
Default-First-Site\mycompa ny-secondD C via RPC
DC object GUID: 844e9cc0-41a9-49da-8449-05 23cf96aa36
Last attempt @ 2013-02-07 10:57:26 was successful.
Default-First-Site\mycompa ny-mainDC via RPC
DC object GUID: 1f5739a0-d579-4c20-97af-90 2d9fc50744
Last attempt @ 2013-02-07 10:57:47 failed, result 1722 (0x6ba):
The RPC server is unavailable.
455 consecutive failure(s).
Last success @ 2013-01-19 23:56:48.
DC=DomainDnsZones,DC=mycom pany,DC=lo cal
Default-First-Site\mycompa ny-mainDC via RPC
DC object GUID: 1f5739a0-d579-4c20-97af-90 2d9fc50744
Last attempt @ 2013-02-07 11:12:11 failed, result 1722 (0x6ba):
The RPC server is unavailable.
2168 consecutive failure(s).
Last success @ 2013-01-20 00:13:35.
Default-First-Site\mycompa ny-secondD C via RPC
DC object GUID: 844e9cc0-41a9-49da-8449-05 23cf96aa36
Last attempt @ 2013-02-07 11:12:32 was successful.
DC=ForestDnsZones,DC=mycom pany,DC=lo cal
Default-First-Site\mycompa ny-mainDC via RPC
DC object GUID: 1f5739a0-d579-4c20-97af-90 2d9fc50744
Last attempt @ 2013-02-07 10:57:05 failed, result 1256 (0x4e8):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
479 consecutive failure(s).
Last success @ 2013-01-19 23:56:49.
Default-First-Site\mycompa ny-secondD C via RPC
DC object GUID: 844e9cc0-41a9-49da-8449-05 23cf96aa36
Last attempt @ 2013-02-07 10:58:08 was successful.
Source: Default-First-Site\mycompa ny-mainDC
******* 51856 CONSECUTIVE FAILURES since 2013-01-20 00:20:17
Last error: 1256 (0x4e8):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
Default-First-Site\mycompa
DC Options: (none)
Site Options: (none)
DC object GUID: e969e570-9334-4cc3-aa80-79
DC invocationID: af1b471f-cd3d-4bad-b7a1-0f
==== INBOUND NEIGHBORS ==========================
DC=mycompany,DC=local
Default-First-Site\mycompa
DC object GUID: a6067ddb-5854-472d-b6ce-fe
Last attempt @ 2013-02-07 11:25:34 was successful.
Default-First-Site\mycompa
DC object GUID: 1f5739a0-d579-4c20-97af-90
Last attempt @ 2013-02-07 11:26:17 failed, result 1722 (0x6ba):
The RPC server is unavailable.
51857 consecutive failure(s).
Last success @ 2013-01-20 00:20:17.
Default-First-Site\mycompa
DC object GUID: 844e9cc0-41a9-49da-8449-05
Last attempt @ 2013-02-07 11:26:17 was successful.
CN=Configuration,DC=mycomp
Default-First-Site\mycompa
DC object GUID: a6067ddb-5854-472d-b6ce-fe
Last attempt @ 2013-02-07 10:57:05 was successful.
Default-First-Site\mycompa
DC object GUID: 844e9cc0-41a9-49da-8449-05
Last attempt @ 2013-02-07 10:57:05 was successful.
Default-First-Site\mycompa
DC object GUID: 1f5739a0-d579-4c20-97af-90
Last attempt @ 2013-02-07 10:57:26 failed, result 1722 (0x6ba):
The RPC server is unavailable.
458 consecutive failure(s).
Last success @ 2013-01-19 23:56:48.
CN=Schema,CN=Configuration
Default-First-Site\mycompa
DC object GUID: a6067ddb-5854-472d-b6ce-fe
Last attempt @ 2013-02-07 10:57:26 was successful.
Default-First-Site\mycompa
DC object GUID: 844e9cc0-41a9-49da-8449-05
Last attempt @ 2013-02-07 10:57:26 was successful.
Default-First-Site\mycompa
DC object GUID: 1f5739a0-d579-4c20-97af-90
Last attempt @ 2013-02-07 10:57:47 failed, result 1722 (0x6ba):
The RPC server is unavailable.
455 consecutive failure(s).
Last success @ 2013-01-19 23:56:48.
DC=DomainDnsZones,DC=mycom
Default-First-Site\mycompa
DC object GUID: 1f5739a0-d579-4c20-97af-90
Last attempt @ 2013-02-07 11:12:11 failed, result 1722 (0x6ba):
The RPC server is unavailable.
2168 consecutive failure(s).
Last success @ 2013-01-20 00:13:35.
Default-First-Site\mycompa
DC object GUID: 844e9cc0-41a9-49da-8449-05
Last attempt @ 2013-02-07 11:12:32 was successful.
DC=ForestDnsZones,DC=mycom
Default-First-Site\mycompa
DC object GUID: 1f5739a0-d579-4c20-97af-90
Last attempt @ 2013-02-07 10:57:05 failed, result 1256 (0x4e8):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
479 consecutive failure(s).
Last success @ 2013-01-19 23:56:49.
Default-First-Site\mycompa
DC object GUID: 844e9cc0-41a9-49da-8449-05
Last attempt @ 2013-02-07 10:58:08 was successful.
Source: Default-First-Site\mycompa
******* 51856 CONSECUTIVE FAILURES since 2013-01-20 00:20:17
Last error: 1256 (0x4e8):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
ASKER
I can see it is failing for one particular domain controller each time.
ok you have somekind firewall or network port blocking software which is blocking your rpc ports
try that
http://blogs.technet.com/b/abizerh/archive/2009/06/11/troubleshooting-rpc-server-is-unavailable-error-reported-in-failing-ad-replication-scenario.aspx
and that
http://blogs.technet.com/b/askds/archive/2009/05/01/sysvol-migration-from-frs-to-dfsr-whitepaper-released.aspx
and that
http://support.microsoft.com/kb/967336
try that
http://blogs.technet.com/b/abizerh/archive/2009/06/11/troubleshooting-rpc-server-is-unavailable-error-reported-in-failing-ad-replication-scenario.aspx
and that
http://blogs.technet.com/b/askds/archive/2009/05/01/sysvol-migration-from-frs-to-dfsr-whitepaper-released.aspx
and that
http://support.microsoft.com/kb/967336
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks seems to be firewall issue
good you found it - and thanks for points:)
still fsr or did you upgrade domain to dfsr?
to check replication run that on domain controllers (from cmd runned as administrator)
repadmin /showrepl
repadmin /replicate
repadmin /syncall
if it detects some errors try that
repadmin /removelingeringobjects
JAN MA CCNA