Groups | Search | Server Info | Login | Register
| From | lingpanda101 via samba <samba@lists.samba.org> |
|---|---|
| Newsgroups | linux.samba |
| Subject | Re: [Samba] AD replication issue |
| Date | 2017-03-14 16:10 +0100 |
| Message-ID | <tkWfi-1T2-75@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <tkDcB-4C4-11@gated-at.bofh.it> <tkEim-5lT-3@gated-at.bofh.it> <tkI2C-8rP-1@gated-at.bofh.it> <tkVsS-1k0-45@gated-at.bofh.it> <tkVMe-1qV-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 3/14/2017 10:29 AM, Arthur Ramsey wrote:
> 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 privacyofficer@mediture.com.
>
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.
--
- James
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Back to linux.samba | Previous | Next — Previous in thread | Next in thread | Find similar
[Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-13 18:40 +0100
Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-13 19:20 +0100
Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-13 19:50 +0100
Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-13 21:00 +0100
Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-13 21:20 +0100
Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-14 01:00 +0100
Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-14 12:20 +0100
Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-14 12:30 +0100
Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-14 15:10 +0100
Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-14 15:20 +0100
Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-14 15:40 +0100
Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-14 16:10 +0100
Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-14 16:30 +0100
Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-14 17:20 +0100
Re: [Samba] AD replication issue Arthur Ramsey via samba <samba@lists.samba.org> - 2017-03-14 18:30 +0100
Re: [Samba] AD replication issue lingpanda101 via samba <samba@lists.samba.org> - 2017-03-14 18:30 +0100
csiph-web