search for: bf06d1b869d2

.... vsc\VSC-DC02 DSA Options: 0x00000001 DSA object GUID: fe066b13-6f9e-4f3c-beb4-37df1292b8cb DSA invocationId: 8a2b1405-07b1-4d92-89dd-1d993e59e378 ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom vsc\DC01 via RPC DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 Last attempt @ Tue Mar 14 09:26:12 2017 CDT was successful 0 consecutive failure(s). Last success @ Tue Mar 14 09:26:12 2017 CDT DC=DomainDnsZones,DC=mediture,DC=dom aws\AWS-DC01 via RPC DSA object GUID: 8b750a53-3d39-4bc...

...sZones,DC=mediture,DC=dom epo\EPO-DC01 via RPC DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 Last attempt@ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=DomainDnsZones,DC=mediture,DC=dom vsc\DC01 via RPC DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=ForestDnsZones,DC=mediture,DC=dom aws\AWS-DC01 via RPC DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @...

...d-42a36ee87590 >> Last attempt@ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> DC=DomainDnsZones,DC=mediture,DC=dom >> vsc\DC01 via RPC >> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >> Last attempt @ NTTIME(0) was successful >> 0 consecutive failure(s). >> Last success @ NTTIME(0) >> >> DC=ForestDnsZones,DC=mediture,DC=dom >> aws\AWS-DC01 via RPC >> DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413...

...001 > DSA object GUID: fe066b13-6f9e-4f3c-beb4-37df1292b8cb > DSA invocationId: 8a2b1405-07b1-4d92-89dd-1d993e59e378 > > ==== INBOUND NEIGHBORS ==== > > DC=DomainDnsZones,DC=mediture,DC=dom > vsc\DC01 via RPC > DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 > Last attempt @ Tue Mar 14 09:26:12 2017 CDT was > successful > 0 consecutive failure(s). > Last success @ Tue Mar 14 09:26:12 2017 CDT > > DC=DomainDnsZones,DC=mediture,DC=dom > aws\AWS-DC01 via RPC >...

I forgot to associate inter-site links (all using default), which fixed a lot though I'm still having an issue. * vsc site o vsc-dc01 o vsc-dc02 * aws site o aws-dc01 * epo site o epo-dc01 * vsc-dc01 => anywhere: OK * vsc-dc02 => anywhere: not replicating * aws-dc01 => anywhere: OK * epo-dc01 => anywhere: OK I've tried with samba_kcc =

...via RPC > DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590 > Last attempt@ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > DC=DomainDnsZones,DC=mediture,DC=dom > vsc\DC01 via RPC > DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 > Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > DC=ForestDnsZones,DC=mediture,DC=dom > aws\AWS-DC01 via RPC > DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa > Last attempt @ NTTIME(0) was successful >...

...Last attempt@ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> DC=DomainDnsZones,DC=mediture,DC=dom >>> vsc\DC01 via RPC >>> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 >>> Last attempt @ NTTIME(0) was successful >>> 0 consecutive failure(s). >>> Last success @ NTTIME(0) >>> >>> DC=ForestDnsZones,DC=mediture,DC=dom >>> aws\AWS-DC01 via RPC >>> DSA object GUID: 8b750a...

...svol folder across domain controllers. I've also reset the access lists on all controllers using samba-tool ntacl sysvolreset. I don't observe any DRS errors or errors in the samba log. samba-tool drs showrepl Default\DC01 DSA Options: 0x00000001 DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 DSA invocationId: 58439028-5404-4b55-b267-671e626644b9 ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom EP\DC02 via RPC DSA object GUID: 9febf392-a39d-4d92-b4d3-4d818a1ce807 Last attempt @ Fri Sep 12 11:53:42 2014 CDT was successful 0 consecutive failure(s). Last success...