[Samba] AD replication issue

[Arthur Ramsey via samba]

I believe the problem is a lack of outbound replication for non PDC
emulator DCs. You'll notice isn't even trying because last successful
was epoch (never) yet there are no errors. Inbound replication for this
DC seems fine.

[***@vsc-dc02 ~]# samba-tool drs showrepl
[...]==== OUTBOUND NEIGHBORS ====

DC=DomainDnsZones,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 @ NTTIME(0)

DC=DomainDnsZones,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 @ NTTIME(0)

DC=ForestDnsZones,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=ForestDnsZones,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=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=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 @ NTTIME(0)

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)

CN=Schema,CN=Configuration,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 @ NTTIME(0)

CN=Schema,CN=Configuration,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)

CN=Schema,CN=Configuration,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)

CN=Configuration,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 @ NTTIME(0)

CN=Configuration,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)

CN=Configuration,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)

==== KCC CONNECTION OBJECTS ====

Connection --
Connection name: 42b18310-000a-498f-911f-d57443724681
Enabled : TRUE
Server DNS name : aws-dc01.mediture.dom
Server DN name : CN=NTDS Settings,CN=AWS-DC01,CN=Servers,CN=aws,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: a96959e9-3a45-4d04-a0d4-9e5b889bb814
Enabled : TRUE
Server DNS name : epo-dc01.mediture.dom
Server DN name : CN=NTDS Settings,CN=EPO-DC01,CN=Servers,CN=epo,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: c2876275-54a6-4eaa-9da1-0c84f24d1b2c
Enabled : TRUE
Server DNS name : dc01.mediture.dom
Server DN name : CN=NTDS Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
--
Arthur Ramsey
System Administrator
Mediture
***@mediture.com
952.400.0323



This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the Mediture Privacy Officer at ***@mediture.com.

[Arthur Ramsey via samba]

Upgraded to 4.6.0 on all nodes. Still seeing the same issue.

If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it doesn't
replicate. If I create it on vsc-dc01 (PDC emulator) then it does
replicate.

Post by Arthur Ramsey via samba
I believe the problem is a lack of outbound replication for non PDC
emulator DCs. You'll notice isn't even trying because last successful
was epoch (never) yet there are no errors. Inbound replication for
this DC seems fine.
[...]==== OUTBOUND NEIGHBORS ====
DC=DomainDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=DomainDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=DomainDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
==== KCC CONNECTION OBJECTS ====
Connection --
Connection name: 42b18310-000a-498f-911f-d57443724681
Enabled : TRUE
Server DNS name : aws-dc01.mediture.dom
Server DN name : CN=NTDS Settings,CN=AWS-DC01,CN=Servers,CN=aws,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: a96959e9-3a45-4d04-a0d4-9e5b889bb814
Enabled : TRUE
Server DNS name : epo-dc01.mediture.dom
Server DN name : CN=NTDS Settings,CN=EPO-DC01,CN=Servers,CN=epo,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: c2876275-54a6-4eaa-9da1-0c84f24d1b2c
Enabled : TRUE
Server DNS name : dc01.mediture.dom
Server DN name : CN=NTDS Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
--
Arthur Ramsey
System Administrator
Mediture
952.400.0323

--
Arthur Ramsey
System Administrator
Mediture
***@mediture.com
952.400.0323



This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the Mediture Privacy Officer at ***@mediture.com.

[lingpanda101 via samba]

Post by Arthur Ramsey via samba
Upgraded to 4.6.0 on all nodes. Still seeing the same issue.
If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it doesn't
replicate. If I create it on vsc-dc01 (PDC emulator) then it does
replicate.

Post by Arthur Ramsey via samba
I believe the problem is a lack of outbound replication for non PDC
emulator DCs. You'll notice isn't even trying because last
successful was epoch (never) yet there are no errors. Inbound
replication for this DC seems fine.
[...]==== OUTBOUND NEIGHBORS ====
DC=DomainDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=DomainDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=DomainDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
==== KCC CONNECTION OBJECTS ====
Connection --
Connection name: 42b18310-000a-498f-911f-d57443724681
Enabled : TRUE
Server DNS name : aws-dc01.mediture.dom
Server DN name : CN=NTDS
Settings,CN=AWS-DC01,CN=Servers,CN=aws,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: a96959e9-3a45-4d04-a0d4-9e5b889bb814
Enabled : TRUE
Server DNS name : epo-dc01.mediture.dom
Server DN name : CN=NTDS
Settings,CN=EPO-DC01,CN=Servers,CN=epo,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: c2876275-54a6-4eaa-9da1-0c84f24d1b2c
Enabled : TRUE
Server DNS name : dc01.mediture.dom
Server DN name : CN=NTDS
Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
--
Arthur Ramsey
System Administrator
Mediture
952.400.0323

Not sure exactly what your issue is but the NTTIME(0) is a bug.

[Arthur Ramsey via samba]

That bug is reported? Do you have a link? You're saying it is just an
issue with the logging or am I correct that this indicates an outbound
replication isn't trying.

Post by lingpanda101 via samba

Post by Arthur Ramsey via samba
Upgraded to 4.6.0 on all nodes. Still seeing the same issue.
If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it
doesn't replicate. If I create it on vsc-dc01 (PDC emulator) then it
does replicate.

Post by Arthur Ramsey via samba
I believe the problem is a lack of outbound replication for non PDC
emulator DCs. You'll notice isn't even trying because last
successful was epoch (never) yet there are no errors. Inbound
replication for this DC seems fine.
[...]==== OUTBOUND NEIGHBORS ====
DC=DomainDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=DomainDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=DomainDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
==== KCC CONNECTION OBJECTS ====
Connection --
Connection name: 42b18310-000a-498f-911f-d57443724681
Enabled : TRUE
Server DNS name : aws-dc01.mediture.dom
Server DN name : CN=NTDS
Settings,CN=AWS-DC01,CN=Servers,CN=aws,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: a96959e9-3a45-4d04-a0d4-9e5b889bb814
Enabled : TRUE
Server DNS name : epo-dc01.mediture.dom
Server DN name : CN=NTDS
Settings,CN=EPO-DC01,CN=Servers,CN=epo,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: c2876275-54a6-4eaa-9da1-0c84f24d1b2c
Enabled : TRUE
Server DNS name : dc01.mediture.dom
Server DN name : CN=NTDS
Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
--
Arthur Ramsey
System Administrator
Mediture
952.400.0323

Not sure exactly what your issue is but the NTTIME(0) is a bug.

--
Arthur Ramsey
System Administrator
Mediture
***@mediture.com
952.400.0323


This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the Mediture Privacy Officer at ***@mediture.com.

[lingpanda101 via samba]

Post by Arthur Ramsey via samba
That bug is reported? Do you have a link? You're saying it is just
an issue with the logging or am I correct that this indicates an
outbound replication isn't trying.

Post by lingpanda101 via samba

Post by Arthur Ramsey via samba
Upgraded to 4.6.0 on all nodes. Still seeing the same issue.
If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it
doesn't replicate. If I create it on vsc-dc01 (PDC emulator) then
it does replicate.

Post by Arthur Ramsey via samba
I believe the problem is a lack of outbound replication for non PDC
emulator DCs. You'll notice isn't even trying because last
successful was epoch (never) yet there are no errors. Inbound
replication for this DC seems fine.
[...]==== OUTBOUND NEIGHBORS ====
DC=DomainDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=DomainDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=DomainDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
==== KCC CONNECTION OBJECTS ====
Connection --
Connection name: 42b18310-000a-498f-911f-d57443724681
Enabled : TRUE
Server DNS name : aws-dc01.mediture.dom
Server DN name : CN=NTDS
Settings,CN=AWS-DC01,CN=Servers,CN=aws,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: a96959e9-3a45-4d04-a0d4-9e5b889bb814
Enabled : TRUE
Server DNS name : epo-dc01.mediture.dom
Server DN name : CN=NTDS
Settings,CN=EPO-DC01,CN=Servers,CN=epo,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: c2876275-54a6-4eaa-9da1-0c84f24d1b2c
Enabled : TRUE
Server DNS name : dc01.mediture.dom
Server DN name : CN=NTDS
Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
--
Arthur Ramsey
System Administrator
Mediture
952.400.0323

Not sure exactly what your issue is but the NTTIME(0) is a bug.

I can't recall if it was reported on Bugzilla. Here is the thread where
Garming mentioned it as such.

https://lists.samba.org/archive/samba/2016-September/203160.html

[Arthur Ramsey via samba]

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 = false and true.

Thanks,
Arthur


This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the Mediture Privacy Officer at ***@mediture.com.

[lingpanda101 via samba]

Post by Arthur Ramsey via samba
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 = false and true.
Thanks,
Arthur
This e-mail and any attachments may contain CONFIDENTIAL information,
including PROTECTED HEALTH INFORMATION. If you are not the intended
recipient, any use or disclosure of this information is STRICTLY
PROHIBITED; you are requested to delete this e-mail and any
attachments, notify the sender immediately, and notify the Mediture

Attempt to manually replicate and see if it corrects your issue.

https://wiki.samba.org/index.php/Samba-tool_drs_replicate

If this doesn't work you can attempt to stop and start the replication
process. I'll explain if needed but I have never actually needed to do
it myself.

[lingpanda101 via samba]

Post by Arthur Ramsey via samba
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 = false and true.
Thanks,
Arthur
This e-mail and any attachments may contain CONFIDENTIAL information,
including PROTECTED HEALTH INFORMATION. If you are not the intended
recipient, any use or disclosure of this information is STRICTLY
PROHIBITED; you are requested to delete this e-mail and any
attachments, notify the sender immediately, and notify the Mediture

I will add that samba will no longer create a full mesh topology to all
DC's by default. This is assuming you have setup sites and services
correctly. Should you require a full mesh, that is where you would
invoke "kccsrv:samba_kcc=false" in your smb.conf.

[Arthur Ramsey via samba]

Manual replication works, but it doesn't stay in sync afterwards.

Thanks,
Arthur

This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the Mediture Privacy Officer at ***@mediture.com.

[lingpanda101 via samba]

Post by Arthur Ramsey via samba
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 = false and true.
Thanks,
Arthur
This e-mail and any attachments may contain CONFIDENTIAL information,
including PROTECTED HEALTH INFORMATION. If you are not the intended
recipient, any use or disclosure of this information is STRICTLY
PROHIBITED; you are requested to delete this e-mail and any
attachments, notify the sender immediately, and notify the Mediture

What is the output of 'samba-tool drs showrepl' for vsc-dc02? You can
manually start and stop replication by issuing

samba-tool drs options vsc-dc02 --dsa-option={+|-}IS_GC |
{+|-}DISABLE_INBOUND_REPL | {+|-}DISABLE_OUTBOUND_REPL

I assume now when you create an object on lets say vsc-dc01, it does not
replicate to vsc-dc02?

[Arthur Ramsey via samba]

Changes replicate to it, but not from it.

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-4bc0-8fe9-9bffa9e413aa
Last attempt @ Tue Mar 14 09:25:09 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:25:09 2017 CDT

DC=DomainDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
Last attempt @ Tue Mar 14 09:25:06 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:25:06 2017 CDT

DC=ForestDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
Last attempt @ Tue Mar 14 09:26:14 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:26:14 2017 CDT

DC=ForestDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
Last attempt @ Tue Mar 14 09:24:42 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:24:42 2017 CDT

DC=ForestDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
Last attempt @ Tue Mar 14 09:24:42 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:24:42 2017 CDT

DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
Last attempt @ Tue Mar 14 09:26:37 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:26:37 2017 CDT

DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
Last attempt @ Tue Mar 14 09:25:07 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:25:07 2017 CDT

DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
Last attempt @ Tue Mar 14 09:25:11 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:25:11 2017 CDT

CN=Schema,CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
Last attempt @ Tue Mar 14 09:26:47 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:26:47 2017 CDT

CN=Schema,CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
Last attempt @ Tue Mar 14 09:24:44 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:24:44 2017 CDT

CN=Schema,CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
Last attempt @ Tue Mar 14 09:24:44 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:24:44 2017 CDT

CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
Last attempt @ Tue Mar 14 09:26:55 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:26:55 2017 CDT

CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
Last attempt @ Tue Mar 14 09:24:45 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:24:45 2017 CDT

CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
Last attempt @ Tue Mar 14 09:24:45 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:24:45 2017 CDT

==== OUTBOUND NEIGHBORS ====

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=DomainDnsZones,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 @ NTTIME(0)

DC=DomainDnsZones,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=ForestDnsZones,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 @ NTTIME(0)

DC=ForestDnsZones,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=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=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 @ NTTIME(0)

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)

CN=Schema,CN=Configuration,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)

CN=Schema,CN=Configuration,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)

CN=Schema,CN=Configuration,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 @ NTTIME(0)

CN=Configuration,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)

CN=Configuration,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 @ NTTIME(0)

CN=Configuration,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)

==== KCC CONNECTION OBJECTS ====

Connection --
Connection name: 298f5484-0e2d-46a1-9505-dfe5eecc1824
Enabled : TRUE
Server DNS name : epo-dc01.mediture.dom
Server DN name : CN=NTDS Settings,CN=EPO-DC01,CN=Servers,CN=epo,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: 42b18310-000a-498f-911f-d57443724681
Enabled : TRUE
Server DNS name : aws-dc01.mediture.dom
Server DN name : CN=NTDS Settings,CN=AWS-DC01,CN=Servers,CN=aws,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: a96959e9-3a45-4d04-a0d4-9e5b889bb814
Enabled : TRUE
Server DNS name : epo-dc01.mediture.dom
Server DN name : CN=NTDS Settings,CN=EPO-DC01,CN=Servers,CN=epo,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: c2876275-54a6-4eaa-9da1-0c84f24d1b2c
Enabled : TRUE
Server DNS name : dc01.mediture.dom
Server DN name : CN=NTDS Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!


This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the Mediture Privacy Officer at ***@mediture.com.

[lingpanda101 via samba]

Post by Arthur Ramsey via samba
Changes replicate to it, but not from it.
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
0 consecutive failure(s).
DC=DomainDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=DomainDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
==== OUTBOUND NEIGHBORS ====
DC=DomainDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
DC=DomainDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=DomainDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=ForestDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
CN=Schema,CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
0 consecutive failure(s).
CN=Configuration,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
0 consecutive failure(s).
==== KCC CONNECTION OBJECTS ====
Connection --
Connection name: 298f5484-0e2d-46a1-9505-dfe5eecc1824
Enabled : TRUE
Server DNS name : epo-dc01.mediture.dom
Server DN name : CN=NTDS
Settings,CN=EPO-DC01,CN=Servers,CN=epo,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: 42b18310-000a-498f-911f-d57443724681
Enabled : TRUE
Server DNS name : aws-dc01.mediture.dom
Server DN name : CN=NTDS
Settings,CN=AWS-DC01,CN=Servers,CN=aws,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: a96959e9-3a45-4d04-a0d4-9e5b889bb814
Enabled : TRUE
Server DNS name : epo-dc01.mediture.dom
Server DN name : CN=NTDS
Settings,CN=EPO-DC01,CN=Servers,CN=epo,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Connection --
Connection name: c2876275-54a6-4eaa-9da1-0c84f24d1b2c
Enabled : TRUE
Server DNS name : dc01.mediture.dom
Server DN name : CN=NTDS
Settings,CN=DC01,CN=Servers,CN=vsc,CN=Sites,CN=Configuration,DC=mediture,DC=dom
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
This e-mail and any attachments may contain CONFIDENTIAL information,
including PROTECTED HEALTH INFORMATION. If you are not the intended
recipient, any use or disclosure of this information is STRICTLY
PROHIBITED; you are requested to delete this e-mail and any
attachments, notify the sender immediately, and notify the Mediture

This isn't correct

CN=Configuration,DC=mediture,DC=dom
vsc\DC01 via RPC

It appears you have a site named "vsc" with a DC name DC01. However you
previously posted what appeared to be DC's named

vsc-dc01 and vsc-dc02.

I would run 'samba-tool drs showrepl' on the other DC's and compare
results. I would expect to see.

CN=Configuration,DC=mediture,DC=dom
vsc\VSC-DC01 via RPC

Can't tell yet if it's a DNS problem or how it happened.

[Arthur Ramsey via samba]

Well vsc-dc01 is actually dc01 for the host name, sorry I forgot about that.

This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the Mediture Privacy Officer at ***@mediture.com.

[lingpanda101 via samba]

Post by Arthur Ramsey via samba
Well vsc-dc01 is actually dc01 for the host name, sorry I forgot about that.
This e-mail and any attachments may contain CONFIDENTIAL information,
including PROTECTED HEALTH INFORMATION. If you are not the intended
recipient, any use or disclosure of this information is STRICTLY
PROHIBITED; you are requested to delete this e-mail and any
attachments, notify the sender immediately, and notify the Mediture

I would try and manually start and stop replication. If that doesn't
work then I'm not sure what the issue is. Maybe samba logs will uncover
something? You could always demote and rejoin the problem server as well.

As I was typing this I just thought of something. Try manually deleting
the automatically generated NTDS connections. Samba should attempt to
recreate them. It may take awhile for Samba to perform this process. You
can try and speed it up by issuing 'samba-tool drs kcc'. Only do this on
your problem DC. You can easily do this using Microsoft's AD sites and
services tool. Same tool you used to create the sites.

[lingpanda101 via samba]

I already tried the manual stop and start already no luck. I just
tried deleting the connections as you recommended, but no luck. I
also have been checking the samba log throughout my troubleshooting,
http://pastebin.com/7FMv8pcu. That log includes when I did the
showrepl, kcc, manual stop / start and manual replication tests as
well as objects created on every DC.
This e-mail and any attachments may contain CONFIDENTIAL information,
including PROTECTED HEALTH INFORMATION. If you are not the intended
recipient, any use or disclosure of this information is STRICTLY
PROHIBITED; you are requested to delete this e-mail and any
attachments, notify the sender immediately, and notify the Mediture

So you deleted the NTDS connections and let Samba recreate? If so, I do
not know what else it could be. Maybe someone else could chime if if
they have thoughts.

[Arthur Ramsey via samba]

I already tried the manual stop and start already no luck. I just tried
deleting the connections as you recommended, but no luck. I also have
been checking the samba log throughout my troubleshooting, but haven't
found anything. Here's the log from vsc-dc02 anyway:
http://pastebin.com/7FMv8pcu. That log includes when I did the
showrepl, kcc, manual stop / start and manual replication tests as well
as objects created on every DC.

This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the Mediture Privacy Officer at ***@mediture.com.