similar to: Problems with samba 4.6.3

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

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 :

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.

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

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, I've having recurring issues with the second DC in my Samba AD domain. I've demoted/removed the second DC a number of times and re-provisioned it. It'll work for a bit and then replication breaks. Since replication is broken I've been doing the following to remove it: DC-02 systemctl stop samba systemctl disable samba DC-01 samba-tool domain demote

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

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

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

On 5/5/2017 10:56 PM, Anantha Raghava wrote: > > 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

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

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 Thu, 28 Feb 2019 18:04:50 -0600 (CST) Mike Ray via samba <samba at lists.samba.org> wrote: > Hello all- > > I am trying to upgrade a old domain to a newer version. The old DCs > are a custom compiled version of Samba, so instead of upgrading the > DCs in place, the plan is to upgrade by joining new DCs to the > domain, replicating data and then shutting down the old

Get this, https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Run it, anonymize it and post it. For both AD-DC's. I want to see a full check on the base setup of the server. If you dont mind ;-) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > basti via samba > Verzonden:

Hai, Before you start, Backup, /etc/ /var/lib/samba better safe than sorry.. Stop samba and related services ( check it at least nmbd smbd winbind samba samba-ad-dc) > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Prunk Dump via samba > Verzonden: woensdag 21 juni 2017 11:57 > Aan: samba at lists.samba.org > Onderwerp:

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

Hello Samba team ! I'am in a very delicate situation. After an upgrade to debian Stretch my DRS stopped working. I have three DCs (fichdc, fichds01, fichds02), all Debian Stretch, all with the same problem. Everything seems to be fine except DRS. -> File shares works -> DNS (with bind9 DLZ) works -> "kinit administrator" works -> "kinit -k FICHDC$" works ->

Dear All, Need some help as I was trying to follow the guide below. https://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC Until the steps of ldbsearch -H /usr/local/samba/private/sam.ldb '(invocationid=*)' --cross-ncs objectguid and my ldbsearch reply with such a result. ldb: unable to dlopen /usr/lib64/samba/ldb/acl.so : /usr/lib64/ldb/libreplace.so: version