similar to: DNS issue.

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

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

Situation: Trying to upgrade Samba from 4.1 to 4.5 without disruption too much by adding new DCs and demoting old ones. After bringing online the first 4.5 DC, I ran `demote --remove-other-dead-server=` on that DC to remove one of the old 4.1 DCs (held no FSMO roles). That seemed to run fine (the DC had been offline for a few weeks at that point and I didn't want to restore it just for

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     

On 2017-04-20 18:38, Rowland Penny wrote: > On Thu, 20 Apr 2017 18:00:24 +0200 > Sven Schwedas via samba <samba at lists.samba.org> wrote: > >> On 2017-04-07 13:44, Sven Schwedas via samba wrote: >>> In the end I just upgraded all DCs to 4.5 and remote-deleted the >>> broken ones. Seemed to work without a hitch, manual removal was >>> only necessary

HI, i just played around with Windows 2008 R2 as ADS Server and two SAMBA 4 as additional DCs. Setting up the Samba 4 DCs works fine. Now I wanted to remove the last Windows DC with dcpromo. It fails with the following statement: Der Vorgang konnte nicht durchgef?hrt werden. Fehler: Active Directory konnte keinen anderen Dom?nencontroller f?r die ?bertragung der verbleibenden Daten

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

Hi Heinz, > 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. you have quite a few objects (>12000) in you main partition. Do you have a large group with all those objects inside? The commit of large group used to result in very very long commit time. There should have been some

On 09/11/2016 01:23 AM, Rowland Penny via samba wrote: > On Sun, 11 Sep 2016 00:48:09 -0600 > "Paul R. Ganci via samba" <samba at lists.samba.org> wrote: >> essentially do what I want? Basically clone the AD on another server. >> Then is it as easy as joining the new server to the domain and then >> demoting the old server? How do others do this task? >

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

Hi all, I have a strange behaviour on our AD. DC=ForestDnsZones,DC=ad,DC=domain,DC=tld Authentification\DC208 via RPC DSA object GUID: 20f711ed-cb02-4543-badb-28d3ed4c4ae1 Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=ForestDnsZones,DC=ad,DC=domain,DC=tld NTDS DN:

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 list, i removed my second DC from the domain, and now the re-join as DC hangs. the join hangs now for ca. 2 hours at the step "Committing SAM database" version: samba 4.5.0 on ubuntu 14.04 with a "strace -p " i see this: strace -p 1793 Process 1793 attached brk(0x35e18000) = 0x35e18000 brk(0x35e39000) = 0x35e39000

Ah, so the error changed.. ? Can you try ? samba-tool domain join empresa.com.br DC -k yes -d 3 --server=samba4-dc01.empresa.com.br? so we try to join through samba4-dc1 and not the windows DC. ? Looking at below again. (objectclass=primaryDomain))' base: 'cn=Primary Domains': No such object: dsdb_search at ../source4/dsdb/common/util.c:4691) and from

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

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,

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 -

On 10/02/2016 06:15 PM, Paul R. Ganci via samba wrote: > 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

Hello guys: I'm running two Zentyal servers with Samba 4.1.17 on each one. We're experiencing some problems such as: - When a user changes his password, it is not replicated the change on secondary DC. - Some Windows machines have reported trust relationship broken. On DC1 I run this: params.c:pm_process() - Processing configuration file "/etc/samba/shares.conf" ldb_wrap open