similar to: Replication failure between 2 Samba4 DCs

On 09/11/2016 10:38 AM, Paul R. Ganci via samba wrote: > On 09/11/2016 01:23 AM, Rowland Penny via samba wrote: > Rowland, thanks for your reply. What you describe is pretty simple in > principle. It is the details about which I am confused. There are 3 > aspects of a Samba 4 AD that have to be properly setup for the AD to > function correctly. Namely the Samba configuration,

Hi All; Can any one help me, i am facing DNS related issue. this is my configuration. Centos 6.2 32bit OS samba4beta3 bind-9.8.3-P1 First i configure samba4 as a domain controller. then i configure other machine as a Additional domain controller, with samba4. but when i run this command it give errors. /usr/local/samba/bin/samba-tool drs showrepl Default-First-Site-Name\PDC DSA Options:

I tried to promote another server as a domain controller so I can get my machines upgraded to Debian 8 Conveniently the samba versions are the same dictator at drakeburner:~$ sudo samba -V Version 4.1.17-Debian root at soothsayer:/etc/samba# samba -V Version 4.1.17-Debian root at soothsayer:/etc/samba# samba-tool drs showrepl Failed to connect host 127.0.0.1 on port 135 -

Hi all, I am currently struggling to remove one of our Samba4 DC from the domain. Some time ago, adding a new Samba DC to our AD did not succeed and I had to demote the new server again. After removal, replication on one of the old/existing DCs got weird. /usr/local/samba/bin/samba-tool drs showrepl gives the following: Standardname-des-ersten-Standorts\dc02 DSA Options: 0x00000001 DSA object

I installed samba as an AD as described on the wiki and set up replication as described on the wiki. I checked and users are not replicated. I am getting the following messages Primary server (SambaCK): LOG: Copyright Andrew Tridgell and the Samba Team 1992-2013 [2013/08/12 08:48:46.359901, 0] ../source4/smbd/server.c:492(binary_smbd_main) samba: using 'standard' process model

G'day All, I've been setting up a new set of DCs, using 4.2.3 and all was going well until I tried to get a 4th DC going. I'm using bind_DLZ, and I think this is where I went wrong. I provisioned the new DC before having set up bind properly (I forgot to "yum install bind bind-util bind-libs") before hand. The provision worked okay, except that it told me

I just added a window server 2008 r2 to be a backup DC for our samba 4.4.5 AD/DC but I am getting an error when trying to manually sync samba to the windows server. I used the link on the wiki site to make the initial sync, which worked great § <https://wiki.samba.org/index.php/Joining_a_Windows_Server_2008_/_2008_R2_ DC_to_a_Samba_AD> Joining a Windows Server 2008 / 2008 R2 DC to a

Hi! I want to get down to the root cause of the issue I am having with my new DC in my domain. I have followed some tutorials on the internet and basically do not get the results. I have 1 old DC, that is providing the AD domain for the whole local network. I wanted to add another one. Both are Ubuntus 16.04, fully updated. I have followed this

Thanks for the fast reply. Sorry - I was not aware that attachments are not forwarded. (All information you requested was included there) I think I have already tried resync via "samba-tool drs replicate" - but better see below the printout of previous attachment "faiserver.log" Thanks for help in advance :) root at faiserver:~# uname -a Linux faiserver.example.corp

Hai,     > When running second command I recieve error: > root at location-000001:~# systemctl start bind9 samba > Failed to start samba.service: Unit samba.service is masked.   ah yes, sorry, that is offcourse samba-ad-dc   >and yep - replication is working then!! :) what i expected the old bug. ;-)   About the other start up for both DC's do the following.  type :   systemctl

Hi, Let's see if any of the questions gets answered or at least I get ponte dto something that can help me. I followed this wiki: http://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC#Getting_ready_for_joining_Samba_as_a_DC_to_an_existing_domain I have my S4 domain running, I compiled and installed another S4 to replicate the first server and joined successfully to the

Hai, ? After upgrading van 4.1.3 to 4.1.4 im getting replication errors. Before the upgrade i had 0 errors..? :-(? ? anyone any sugestions? ? ? samba-tool drs showrepl.? multiple messege?like below.? ? ??????????????? DSA object GUID: a1561f3a-cf45-4aa6-85d7-0e1a1b05e0a4 ??????????????? Last attempt @ Fri Jan 17 08:27:12 2014 CET failed, result 2 (WERR_BADFILE) ??????????????? 248 consecutive

Hi , Thank you for your input. I have had tried all of the escape characters you have have tested with but I have had no luck with them. I am curious to know which versions of net have you been tested with? I do agree that the best practice for this is to remove "-" from the beginning of the object name, However, seeing that it can be created that way allowed, I would like to find a

Hi, I have downgraded samba 4.7 (van-belle repository) to 4.5.16 from the Debian 9 repository and was able to put it in the domain. root at samba4-new-dc:/etc/samba# samba -V Version 4.5.16-Debian samba-tool domain join empresa.com.br DC -k yes -d 3 --server= samba4-dc1.empresa.com.br root at samba4-new-dc:/etc/samba# samba-tool domain join empresa.com.br DC -k yes -d 3

hi again, now the join finished but ... i have a high CPU load caused by a samba-process. Samba is consuming 100% of one CPU and the replication fails. Is my AD to large???? root at dc2:# samba-tool drs showrepl Default-First-Site-Name\DC2 DSA Options: 0x00000001 DSA object GUID: e9d31c7e-acb3-4473-823a-39b06ab9fa95 DSA invocationId: 49a80da8-975f-49ef-834b-224b2bbf0805 ==== INBOUND

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 Denis, yes, the problem initiated after changing the primary group of all my 11034 users. I changed the primary group to different groups. This caused that now every user is member of the LDAP object "Domain users" ldapsearch -LLL -x -h dc1 -x -b "cn=domain users,cn=users,dc=example,dc=net" member | grep ^member: | wc -l 11034 After this action the replication

Hi, the only thing i did, was to assign every user to a ohter group. After this i changed the primary group to this new groups and the samba-server itself assigned the users to the group "domain users"automatically (attribute: member). Now i try to revert this and to rechange the primary group to 513. So i can have again a Domain users object with small number of members. Thanx

On 2016-09-24 06:53, lingpanda101 at gmail.com wrote: > On 9/22/2016 6:31 PM, Garming Sam wrote: >> On 23/09/16 00:59, lingpanda101 at gmail.com wrote: >>> For clarification I'll add a few things. >>> >>> I initially deleted all the NTDS site links for each site and allowed >>> the new KCC to create them. However it did not create them I believe

No answer from anyone from the community so I managed by myself, answering also questions by myself. So... Question 1: How can a DC relies on deleted object to perform replication? That is a bug from Samba (the new KCC?). Sorry to say that but what else? Deleted object are objects which are not in use. They have something to do perhaps with replication but they MUST NOT be used as valid source