similar to: ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (-1073610699, 'The operation cannot be performed.')

Hello there, I have a problem with replication between two domain controllers, dc1 and dc2. Distribution: Debian 8.5 Samba-Distribution: sernet-samba 4.3.11-14 The replication on dc2 working fine without any failures. But the synchronization on dc1 gives the failure "WERR_BAD_NETPATH". Because the message "BAD_NETPATH" I checked the DNS-resolution:

Am 23.08.2016 um 15:36 wrote Heinz Allerberger via samba: > Hello there, > > I have a problem with replication between two domain controllers, dc1 > and dc2. > Distribution: Debian 8.5 > Samba-Distribution: sernet-samba 4.3.11-14 > > The replication on dc2 working fine without any failures. > But the synchronization on dc1 gives the failure "WERR_BAD_NETPATH".

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, I performed the procedures below on Samba4-DC1 (Master) and apparently everything went fine. /etc/init.d/samba-ad-dc stop sed -i -e 's/${DOMAINDN}/DC=empresa,DC=com,DC=br/g' \ -e 's/${NETBIOSNAME}/SAMBA4-DC1/g' \ -e 's/${NISDOMAIN}/empresa/g' \ /tmp/ypServ30.ldif root at samba4-dc1:/tmp# ldbmodify -H /var/lib/samba/private/sam.ldb

Hello everyone, I have setup two Samba AD DC's with BIND9_DLZ dns backend. faiserver.example.corp is one of them hosting all FSMO Roles. location-000001.example.corp is the second one. Both are in different subnets but can reach each other. Unfortunately replication only works from faiserver.example.corp -> location-000001.example.corp. In the other direction location-000001.example.corp

Hai,   As extra on Rowland comment..  Your config looks ok as said, i did see..   smb.conf  map to guest = bad user         < remove it.   Bad User - Means user logins with an invalid password are rejected, unless the username does not exist, in                       which case it is treated as a guest login and mapped into the guest account. and you want that for a AD DC setup?  you might

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 :) )

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 ====

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I just set up a Domain with two DCs. I use Debian jessie the debian-pakages. And bind9 also from the debian repositories. After setting up the first DC everything was working fine. The nameresolution of hosts ans SRV-records worked. Then I set up a second DC also everything aut of the debian-box with bind9 as nameserver. The

Ok, some more resolving things to fix.   On both DC's few things to edit. In resolv.conf, the order is important here and dont point to nameserver 127.0.0.1 for the DC's.   DC1. file: /etc/resolv.conf  search example.corp nameserver IP_DC1 nameserver IP_DC2 nameserver 8.8.4.4 /etc/hosts IP_DC1 hostname.internal.example.com hostname IP_DC2 hostname.internal.example.com hostname     

Hi all, I'm running in circles trying to debug replication failures on samba 4.7.6: dc00 : is a VM on KVM host (attached to a bridge on local LAN) dc01 : is a similarly configured VM on another KVM host. I've forcibly demoted and re-promoted dc01 but I still cannot get automatic replication to work: root at dc00 ~]# samba-tool drs showrepl Krynn\DC00 DSA Options: 0x00000001 DSA

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

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')

Hi, I have been trying for days to solve this to no avail. I have taken over the IT responsibilities at a small school and am trying to get my head around their network and why they are having problems. They have 3 servers, Matthew, Genesis and Luke. Matthew is a Windows 2008 R2 server and holds all the FSMO roles but appears to be screwed up. It won't replicate with anything and randomly

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:~ #

Hi there. I'm trying to upgrad from 4.7.7 to 4.9.4. I built from source, running on centos 7.6 on a Raspberry Pi. When testing on a secondary DC, my "samba-tool drs showrepl" errors out with: ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to dc02.rvx.is > failed - drsException: DRS connection to dc02.rvx.is failed: (8, >

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

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

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

Hai, ? Im having the same problems as discribed here. https://lists.samba.org/archive/samba/2013-June/173981.html? samba4 install on debian with sernet samba. i did this about 10 times now, and this is the first time i have this. i've tried to update manualy. samba-tool drs replicate dc2 dc1 DC=INTERNAL,DC=DOMAIN,DC=TLD ? but results in : ERROR(<class