similar to: Replication issues / local DRS authentication failure

Hi. Here is my problem. I have 2 DC (DC1, DC2) From DC1 I run samba-tool drs showrepl DC1 ------------------------------------------------------------------------------------- INBOUND NEIGHBORS : OK OUTBOUND NEIGHBORS : OK ==== KCC CONNECTION OBJECTS ==== Connection -- Connection name: 179ef6ba-a138-46d7-9a64-880ab4608b04 Enabled : TRUE Server DNS name :

Hi list, I'm running into issues with Samba 4.5.16-Debian. I am trying to get 3 DCs to talk to each other and replicate. DC1 and DC3 are on the same subnet; DC2 is on another subnet, accessible by IP. Currently, no firewalls on any of the DCs. Issue 1 - When I run "samba-tool drs showrepl", I get various results: DC1 - Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2

Samba 4.5.1 (started with this version as well) I started with 3 domain controllers, DC1 and DC2 at the hub, and another, DC3 as a spoke. Everything was running smoothly with this config. No problems with 'samba-tool drs showrepl'. As soon as I started adding more 'spoke' domain controllers I'm getting timeouts in the 'samba-tool drs showrepl' command. I believe

Hello James, Even after setting the rfc2307 in smb.conf replication error continues and password change error continues. Error thrown while forcing replication is shown below. ------------------------------------------------------------------- Even after setting RFC, DC2 is not getting synced from DC1. Connection time out error comes. #samba-tool drs replicate DC2.KTKBANKLTD.COM

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

I have two DC with Samba 4.2.1 and now I have set up a third DC with Samba 4.6.3. I have executed the command: samba-tool domain join empresa.com.br DC -U "EMPRESA\administrator" --dns-backend = SAMBA_INTERNAL And everything went well, however with the command: samba-tool drs showrepl The following message appears: root at dc3:/home/marcio# /usr/local/samba/bin/samba-tool drs

Hello. We're trying to integrate Samba 4 as a DC in production. We aim to replace our only Windows 2003 Enterprise R2 Russian DC with 2 Samba DCs. However, we've got a replication problem, we aren't shure is it a bug or misconfiguration. Both Windows and Samba DCs are virtual amd64 machines, running under the control of Xen (so, at least the time is the same). Windows VM has GPLPV

Hi Aleksey, did you find any solution for this? I just updated from 4.8.2 to 4.8.3 and had very similar effects: Login was no longer possible with 4.8.3 - log file was full of "ldb: Failed to unlock db" messages. I had to downgrade to 4.8.2 in order to make samba work again. Bye, Marcel June 28, 2018 10:28 AM, "Aleksey Vladimirov via samba" <samba at

Hello James, To your questions: *"Are DC1 and DC2 in the same geographical location?"* Yes, they are in same location, & they are in the same subnet as well. *"I'm also unclear from your message if you are still having password issues or not."* **It appears to have been resolved. When we randomly checked, users were able to change their passwords. However

After update I have got this: samba-tool drs kcc -Uadm2 -d 9 INFO: Current debug levels: all: 9 tdb: 9 printdrivers: 9 lanman: 9 smb: 9 rpc_parse: 9 rpc_srv: 9 rpc_cli: 9 passdb: 9 sam: 9 auth: 9 winbind: 9 vfs: 9 idmap: 9 quota: 9 acls: 9 locking: 9 msdfs: 9 dmapi: 9 registry: 9 scavenger: 9 dns: 9 ldb: 9 tevent: 9 auth_audit: 9

Hello Replication failed . Forced replication with samba-tools also , with output as below : /usr/local/samba/bin/samba-tool drs replicate dc1 dc2 CN=Computers,DC=vizavi,DC=inc,dc1.vizavi.inc Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for e3514235-4b06-11d1-ab04-00c04fc2dcd2 at ncacn_ip_tcp:dc1[1024,seal] NT_STATUS_NET_WRITE_FAULT ERROR(<class

I removed a DC using the DC removal tool mentioned in http://gallery.technet.microsoft.com/scriptcenter/d31f091f-2642-4ede-9f97-0e1cc4d577f3 as https://bugzilla.samba.org/show_bug.cgi?id=10734 prevents normal DC demotion. The DC was still all over in DNS, so I had to pick it out. Now replication between the remaining three DCs is broken [root at larkin26 ~]# samba-tool drs showrepl

Hi Guys, I have now updated to 4.5.0 - thank you to all the team for your efforts on this :) I was excited to read in the release notes that there were many replication improvements, and I have run 'samba-tool dbcheck --cross-ncs --fix' on all my DCs; there were many, many replPropertyMetaData and other errors which have now been found and fixed - thanks! However, I think something

Hi, It seems unlikely that the KCC is the cause of these issues. The KCC is only responsible for telling who to connect (and when) and doesn't actually affect any underlying network connectivity. Connectivity between the spokes should not be required and the communication between them is usually just some stale data. But none of that should affect either of these commands. Unless the DRS

Hi, I get the following error when I am trying to check the replication status of my samba4 dc: ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to nidy. failed - drsException: DRS connection to nidy. failed: (-1073741772, 'The object name is not found.') File "/usr/lib64/python2.7/site-packages/samba/netcmd/drs.py", line 39, in drsuapi_connect

Am 12.10.2016 um 20:17 schrieb lingpanda101--- via samba: > On 10/12/2016 1:57 PM, Ronny Forberger via samba wrote: >> Hi, >> >> I get the following error when I am trying to check the replication >> status of my samba4 dc: >> >> ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to nidy. >> failed - drsException: DRS connection

On 5/5/2017 11:08 AM, Anantha Raghava wrote: > > Hello James, > > Even after setting the rfc2307 in smb.conf replication error continues > and password change error continues. Error thrown while forcing > replication is shown below. > > ------------------------------------------------------------------- > Even after setting RFC, DC2 is not getting synced from DC1.

On 10/20/20 3:25 PM, Rowland penny via samba wrote: > On 20/10/2020 21:09, Derek Lambert wrote: >> I really dislike Raspian, and there's not a 64bit release yet. >> >> Does the official Debian distro use Heimdal? Ubuntu? > > Cannot really speak for the rpi, I just use mine as a Unix domain member running > raspbian, but it is basically only the distros based on

Am 13.10.2016 um 16:28 schrieb lingpanda101 at gmail.com: > On 10/13/2016 10:19 AM, Ronny Forberger wrote: >> >> Am 12.10.2016 um 20:17 schrieb lingpanda101--- via samba: >>> On 10/12/2016 1:57 PM, Ronny Forberger via samba wrote: >>>> Hi, >>>> >>>> I get the following error when I am trying to check the replication >>>>

Am 13.10.2016 um 16:54 schrieb lingpanda101 at gmail.com: > On 10/13/2016 10:37 AM, Ronny Forberger wrote: >> >> Am 13.10.2016 um 16:28 schrieb lingpanda101 at gmail.com: >>> On 10/13/2016 10:19 AM, Ronny Forberger wrote: >>>> Am 12.10.2016 um 20:17 schrieb lingpanda101--- via samba: >>>>> On 10/12/2016 1:57 PM, Ronny Forberger via samba wrote: