similar to: One DC not replicated

Hi, I have three Samba Domain Controllers, two in the LAN local network (dc1 and dc2) and one in a remote network which is accessible from the LAN through a VPN connection (dc4). Every domain controller can reach every other domain controllers, and every type of traffic is permitted by firewalls, they can ping and access to every TCP and UDP ports. Checking the Samba replication I see that the

On 29/10/2019 00:47, Zombie Ryushu via samba wrote: > I am having issues with Samba DC replication between two directly > connected DCs. > > I don't understand what is wrong or how to fix it. Can someone advise? > > $ sudo samba-tool drs showrepl > Default-First-Site-Name\OLYMPIA > DSA Options: 0x00000001 > DSA object GUID: 50507d18-c8ee-4ef4-bbda-4d0d9bc31caa >

On 10/29/19 6:14 AM, L.P.H. van Belle via samba wrote: > I'm pretty sure this is a resolving problem. > > Can you verify this: > https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record > Especialy these : for both guids and cross check if from both servers. > host -t CNAME 50507d18-c8ee-4ef4-bbda-4d0d9bc31caa._msdcs..... > > Can you post from both

I'm pretty sure this is a resolving problem. Can you verify this: https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record Especialy these : for both guids and cross check if from both servers. host -t CNAME 50507d18-c8ee-4ef4-bbda-4d0d9bc31caa._msdcs..... Can you post from both server. /etc/hosts /etc/resolv.conf host servername host fqdn host servername @dns othere

I am having issues with Samba DC replication between two directly connected DCs. I don't understand what is wrong or how to fix it. Can someone advise? $ sudo samba-tool drs showrepl Default-First-Site-Name\OLYMPIA DSA Options: 0x00000001 DSA object GUID: 50507d18-c8ee-4ef4-bbda-4d0d9bc31caa DSA invocationId: d7f3c683-fcf2-473c-be01-a6f58af6cb88 ==== INBOUND NEIGHBORS ====

----- Messaggio originale ----- Da: "Rowland Penny via samba" <samba at lists.samba.org> A: "samba" <samba at lists.samba.org> Cc: "Rowland Penny" <rpenny at samba.org> Inviato: Mercoled?, 8 marzo 2023 17:01:34 Oggetto: Re: [Samba] Unable to "rejoin" existing DC after upgrade (infamous WERR_FILE_NOT_FOUND) Please do not 'cc' me or

On 08/03/2023 17:09, Fabrizio Rompani via samba wrote: > > yes , after join completed . > error is trigged with the command : > > root at landc:~# samba-tool drs showrepl --summary > There are failing connections > Failing outbound connections: > CN=Configuration,DC=domain,DC=lan > Default-First-Site-Name\NEXTCLOUD via RPC > DSA object

08.03.2023 20:09, Fabrizio Rompani via samba ?????: ... > root at landc:~# samba-tool drs showrepl --summary > There are failing connections > Failing outbound connections: > CN=Configuration,DC=domain,DC=lan > Default-First-Site-Name\NEXTCLOUD via RPC > DSA object GUID: 3fa4ff9a-7fdc-4912-ad73-08b98f6bf347 > Last attempt @ Wed Mar 8

Hello! Please help me with the following issue: My employer has an Active Directory with four samba4 domain controllers named dc1, dc2, dc3, dc4. `samba-tool drs showrepl` on dc2 constantly shows DC=mydomain Default-First-Site-Name\DC1 via RPC DSA object GUID: 48bff36e-35e2-4b09-9e40-9d73b9a5387b Last attempt @ Sat Aug 12 21:48:43 2017 MSK failed,

Dear list, in this corona crisis a delivery of a AD to a location abroad takes longer than I expected. I demoted the AD which is in delivery with samba-tool domain demote --remove-other-dead-server=ADDC3 If I know trigger a samba-tool drs showrepl I still see him in the list: CN=Configuration,DC=example,DC=com ??? NTDS DN: CN=NTDS

Hi. As happened some weeks ago, here I am again updating an old Samba 4.14.x network to a current version. The server hosting the FSMO roles is a Debian10 with 4.14.14, while the third node is a Ubuntu 18 running LinuxSchools build 4.14.8. We started from a Ubuntu 20.04 server running Louis builds. We demoted the node and joined it back to the domain with 4.17.5 from Michael. Although on the

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. On 03/13/2017 01:45 PM, lingpanda101 via samba wrote: > On 3/13/2017 2:15 PM, Arthur Ramsey via samba wrote: >> Upgraded to 4.6.0 on all nodes. Still seeing the same issue. >> >> If I create an

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. On 03/13/2017 12:13 PM, Arthur Ramsey wrote: > > I believe the problem is a lack of outbound replication for non PDC > emulator DCs. You'll notice isn't even

On 2016-09-24 06:53, lingpanda101 at gmail.com wrote: > On 9/22/2016 6:31 PM, Garming Sam wrote: >> On 23/09/16 00:59, lingpanda101 at gmail.com wrote: >>> For clarification I'll add a few things. >>> >>> I initially deleted all the NTDS site links for each site and allowed >>> the new KCC to create them. However it did not create them I believe

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. [root at vsc-dc02 ~]# samba-tool drs showrepl [...]==== OUTBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom aws\AWS-DC01 via RPC DSA object GUID:

On 3/13/2017 2:15 PM, Arthur Ramsey via samba wrote: > 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. > > On 03/13/2017 12:13 PM, Arthur Ramsey wrote: >> >> I believe the problem is a lack

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 >

Ok here is the output: If the output of the other DCs is needed let me know. On the other DCs there are kcc connections for all other DCs. Just not on dc1. [root at dc1 ~]# samba-tool drs showrepl Default-First-Site-Name\DC1 DSA Options: 0x00000001 DSA object GUID: 1781607c-77e8-405d-8c3a-b7e142dd30c4 DSA invocationId: dc096a8a-773d-4a63-8e2a-288ab747557b ==== INBOUND NEIGHBORS ====

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

On 9/22/2016 6:31 PM, Garming Sam wrote: > On 23/09/16 00:59, lingpanda101 at gmail.com wrote: >> For clarification I'll add a few things. >> >> I initially deleted all the NTDS site links for each site and allowed >> the new KCC to create them. However it did not create them I believe >> correctly. By that I mean it defined what appeared to be a bridgehead