similar to: replication stopped working after upgrade from 4.11 to 4.12.3

Hello everyone, I have setup two Samba AD DC's running Debian 9 with BIND9_DLZ dns backend. Both are running Samba 4.5.16 - I know it is already very old version but this is the default one coming with debian stretch repo. (I will upgrade to Debian buster - and with this to newer Samba version - as soon as it is released stable and I could test the upgrade correctly :) )

Hello,   I am once again having troubles with a setup of a samba 4 DC and a Windows Server 2008R2 DC. Replication between these two stopped a few days ago. Since then the logs on the samba server are flooded with:   Failed to bind to uuid e3514235-4b06-11d1-ab04-xxxxxxxxxxxx for

On Sat, 6 Apr 2019 10:58:15 +0200 Martin Krämer via samba <samba at lists.samba.org> wrote: > Hello everyone, > > I have setup two Samba AD DC's running Debian 9 with BIND9_DLZ dns > backend. Both are running Samba 4.5.16 - I know it is already very > old version but this is the default one coming with debian stretch > repo. (I will upgrade to Debian buster - and with

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

Hi, I have replications problems on one of my server. Replication was working since month and yet stopped working. on the remote server: islad01:~ # samba-tool drs showrepl | more Default-First-Site-Name\ISLAD01 DSA Options: 0x00000001 DSA object GUID: 3fe6bc7c-1116-4344-96a6-c58c43bc217f DSA invocationId: 89351eec-7207-45f5-b6b9-cebfcacfd0e3 ==== INBOUND NEIGHBORS ====

Hi LingPanda101, .... > > DC=domain,DC=local > site-c\DUNDC1 via RPC > DSA object GUID: a216e718-488f-4821-8d9c-a399e6789222 > Last attempt @ NTTIME(0) was successful > 0 consecutive failure(s). > Last success @ NTTIME(0) > > DC=ForestDnsZones,DC=domain,DC=local > site-c\DUNDC2 via RPC

Hi Marc, Thanks for your reply. On 18/07/2014 21:19, Marc Muehlfeld wrote: > Hello Fernando, > > Am 18.07.2014 20:14, schrieb Fernando Rodriguez: >> I am having a problem while demoting a DC. >> >> The DC i want to demotes is still online. When i try to use the command >> samba-tool domain demote this is the message i get: >> >> root at

Hi all, I am currently struggling to remove one of our Samba4 DC from the domain. Some time ago, adding a new Samba DC to our AD did not succeed and I had to demote the new server again. After removal, replication on one of the old/existing DCs got weird. /usr/local/samba/bin/samba-tool drs showrepl gives the following: Standardname-des-ersten-Standorts\dc02 DSA Options: 0x00000001 DSA object

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

Samba4 latest on FreeBSD8.1RC2 built and running as a joined DC: 81rc2# pwd /usr/local/samba/sbin 81rc2# ps -ax | grep samba 92436 ?? Ss 0:00.24 ./samba 92437 ?? S 0:00.01 ./samba 92438 ?? I 0:00.04 ./samba 92439 ?? S 0:00.01 ./samba 92440 ?? S 0:00.00 ./samba 92441 ?? S 0:00.00 ./samba 92442 ?? S 0:00.00 ./samba 92443 ?? S 0:00.01 ./samba

Hello guys: I'm running two Zentyal servers with Samba 4.1.17 on each one. We're experiencing some problems such as: - When a user changes his password, it is not replicated the change on secondary DC. - Some Windows machines have reported trust relationship broken. On DC1 I run this: params.c:pm_process() - Processing configuration file "/etc/samba/shares.conf" ldb_wrap open

I have a Samba managed Windows domain with 3 Domain Controllers: dc1, dc2 and dc-dc. All three PDC runs on Samba version 4.6.7-Ubuntu on Ubuntu Xenial. The problem: the Domain Controller dc-dc is not correctly replicated: ======================================================================== root at dc2:/# samba-tool drs showrepl ldb_wrap open of secrets.ldb GENSEC backend