similar to: Samba4 Replication Errors

I started with one dc, 'dc1', running samba v4.0.21, in subnet1. I successfully added two more dc's, 'dc2' and 'dc3', both running samba v4.0.24, both in subnet2. There are several firewalls between subnets 1 & 2. I continued to make firewall holes on behalf of msad after I added dc's 2 & 3. I.e. when they were added, there were patterns of communication

I have two zentyal servers running samba, one as PDC and one as additional DC. It was working perfectly until last week. Now if I add a new computer to the domain it appears on one of our DCs but not on the other one. Same with users, if I deactivate one it doesn't get deactivated on the other DC. I was waiting more than a day to make sure it's not syncing . If I execute 'sudo

I did, but I don't know how to decypher it. Here's a 1.5 second snippet of the the strace -p PID command. Jeff Donaldson Technology Director Newark Charter School jeff.donaldson at ncs.k12.de.us (302) 369-2001 ext: 425 ________________________________________ From: Jeremy Allison <jra at samba.org> Sent: Thursday, April 16, 2015 6:49 PM To: Donaldson Jeff Cc: samba at

Greetings, I'm currently experiencing an issue with two of my three Samba servers where one Samba process is pegging the CPU usage and eating up a lot of virtual and resident memory. While this is happening I get a "ERROR(runtime): DsReplicaGetInfo of type 0 failed - (-1073610723, 'NT_STATUS_RPC_PROTOCOL_ERROR')" error when I try to run the samba-tool drs showrepl command.

My apologies, went to paste and accidentally sent the message...see below for rest of detail. Greetings, I'm currently experiencing an issue with two of my three Samba servers where one Samba process is pegging the CPU usage and eating up a lot of virtual and resident memory. While this is happening I get a "ERROR(runtime): DsReplicaGetInfo of type 0 failed - (-1073610723,

On Thu, Apr 16, 2015 at 02:33:20PM +0000, Donaldson Jeff wrote: > My apologies, went to paste and accidentally sent the message...see below for rest of detail. > > > Greetings, > > > I'm currently experiencing an issue with two of my three Samba servers where one Samba process is pegging the CPU usage and eating up a lot of virtual and resident memory. While this is

I have a server that is not replicating correctly, but passes all the tests listed here: https://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC In particular running # host -t CNAME 976c9c86-288d-483e-baec-7043a9c4a6cd._msdcs.ncs.k12.de.us 976c9c86-288d-483e-baec-7043a9c4a6cd._msdcs.ncs.k12.de.us is an alias for ncssamba2.ncs.k12.de.us. returns correct information on all DCs.

I have the following setup: PDC: Samba 3.0.37 on Solaris 10 BDC1: Samba 3.0.37 on Solaris 10 BDC2: Samba 3.4.3 on Solaris 10 Samba 3.0.37 is the bundled version of Samba. Samba 3.4.3 is compiled from source. BDC2 is a recent addition to the network. All machine use LDAP as the backend for everything. They use winbind to handle a domain trust with another domain, but otherwise

OK, tried that. Kicked myself for not trying earlier... but it didn't work. In fact, the error has got worse. Now when I try to go from Genesis to Luke I get: sudo samba-tool drs replicate luke genesis DC=kcs,DC=local -Udomainadmin . . ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (1359, 'WERR_INTERNAL_ERROR')

I have DC on samba 4.5.2 (pdc) Also I have additional DC on Win2008 R2. (bdc) pdc and bdc just host names When I trying to replicate samba to windows: pdc:~ # samba-tool drs replicate bdc pdc DC=tidykzn,DC=local Replicate from pdc to bdc was successful. pdc:~ # samba-tool drs replicate bdc pdc CN=Schema,CN=Configuration,DC=tidykzn,DC=local Replicate from pdc to bdc was successful. pdc:~ #

I'd try to rejoin the faulty DC instead of copying sam.ldb files. I guess there are unique DC specific entries in the local database. Can be samba-tool replicate works if you try the push the settings from an other dc or pull em on the faulty dc. What command did you try andn on what dc? Am 25.02.2016 um 14:02 schrieb Sébastien Le Ray: > Still the same error… > > ERROR(<class

My samba4.11 server will only replicate one way: windows -> samba. Replication from samba -> windows fails. Details follow. I have a Samba 4.11 domain controller (fs1) that was added to an existing domain that had a Windows Server 2003R2 domain controller (fs) and Windows Small Business Server 2011 (sbs). fs1 is running on Debian 7.6 My issues seems similar to

Hi together, Demoting from a Win-Server-Based Active Directory fails root at srvf01:~# samba-tool domain demote --server windc-server -UAdministrator Using srv15.lan.compumaster.de as partner server for the demotion Password for [COMPUMASTER\Administrator]: Desactivating inbound replication Asking partner server windc-server to synchronize from us Error while demoting, re-enabling inbound

hi, After a "samba-tool drs showrepl" I saw that there had been an error in the replication of ForestDnsZones. I ran a "samba-tool drs replicate dc2 dc3 DC=ForestDnsZones,DC=campus,DC=sertao,DC=ifrs,DC=edu,DC=br -d10" and the error below occurred. ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed

Hi, Many of these syncing problems were solved in Samba 4.7 (and probably a few more in 4.8). There were a number of unresolved locking issues that we uncovered as well as some inconsistencies with Windows replication. I would try join a DC with one of the latest Samba versions and see if your problems persist. Cheers, Garming On 21/06/18 21:35, Chris Lewis via samba wrote: > Hello, >

Hi, When we try replicate domain tree from Win DC to Samba DC we have timeout error: ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (-1073741643, '{Device Timeout} The specified I/O operation on %hs was not completed before the time-out period expired.') File

This is probably a frequent problem, but I haven't been able to find an answer. I recently installed samba 2.0.5a on Sun Solaris 2.6 server. There is only one share on the server that I want to be accessible. I have set up the share using the following smb.conf file: (obviously, the specific info has been changed). [global] netbios name = XXX #Server has different name guest account =

Hello, I set up a domain with two DCs (dns-backend is BIND9_DLZ) on a Debian 10 system. I used either the Debian-packages or the Packages from Louis (4.12.8). I created an Ansible-role to setup everything, starting from installing the packages over doing the provision/join up to change the settings for bind9. The first DC runs fine. After the reboot services are all present, allthe SRV Record for

Hi all, Seems we're in much more trouble now... Yesterday I lowered the dn stombstone lifetime from 180 to 60, to reduce the size of DC=DomainDnsZones, and ever since, things have become terrible... The situation now: I have separate fileserver, and three DC3's, all on the same subnet, kvm virtual machines, all running sernet-samba. (4.1.7 and 4.1.9) == on DC3 == DNS queries for my

I'm using samba 4.0.3 (host samba01) and samba 4.0.5 (samba02) as DCs. samba01 already existed and I used samba-tool domain join to join samba02 to domain samba.x.y.z. This worked quiet well, but now replication fails: /usr/local/samba/bin/samba-tool drs showrepl ==== INBOUND NEIGHBORS ==== ... DC=DomainDnsZones,DC=samba,DC=x,DC=y,DC=z Default-First-Site-Name\SAMBA01 via RPC