similar to: samba4 replication failed after upgrade

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

Just to ask. Anyone can shard some light on that wrong is that? Thank you. Min Wai Chan <dcmwai at gmail.com> 於 2015年7月30日 星期四寫道： > Dear All, > > Recently I notice that sometime the AD DC will die sometime. > Any one have see this issue before? > > And yesterday case lead me to believes that this error message was the > issue... > They are repetitive and thus I

What Samba version are you using? I have seen a similar problem triggered by connectivity issues between the DCs. What's the output from samba-tool drs showrepl? Still, I haven't found a solution... On Sat, Aug 1, 2015 at 5:30 AM, Min Wai Chan <dcmwai at gmail.com> wrote: > Just to ask. > Anyone can shard some light on that wrong is that? > > Thank you. > > Min

Dear All, Recently I notice that sometime the AD DC will die sometime. Any one have see this issue before? And yesterday case lead me to believes that this error message was the issue... They are repetitive and thus I only show 2... [2015/07/29 00:00:04.620033, 0] ../source4/librpc/rpc/dcerpc_util.c:681(dcerpc_pipe_auth_recv) Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for

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 :

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

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.

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

Good afternoon, tell me, this error occurs on the domain controller samba v 4.19.0, I paired the domain controller with sssd so that authentication occurs under domain accounts on the domain controller, but as you know, sssd changes the machine password every 30 days if this option is not disabled ad_maximum_machine_account_password_age = 0 I haven?t disabled it for 30 days and as I understand it,

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

I have 1 DC in the UK running samba4 fine for the last 6 weeks now am trying to join another this one is in shanghai connected via VPN when joining am getting the following error samba-tool domain join sondrel.com DC -Uadministrator --realm=sondrel.com--dns-backend=BIND9_DLZ Finding a writeable DC for domain 'sondrel.com' Found DC uk-dc01.sondrel.com Password for

and you have added the following to the /etc/hosts 172.16.99.3 pdc.domain.co.id pdc and you did setup your krb5.conf in that way you point directly to the correct hosts without the use of a search like: [logging] default = FILE:/var/log/krb5libs.log kdc = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log [libdefaults] default_realm = SMBDOM.EXAMPLE.COM dns_lookup_realm =

hi all i have problem with my multi-site AD-DC installation, one of my DC, suddently cant start well, i think problem(corrupt) with the LDAP database then i try to re join it, but every time i try to join it i always has issue like this /Finding a writeable DC for domain 'domain.co.id' Found DC pdc.domain.co.id Password for [domain\administrator]: workgroup is domain realm is