similar to: Bind9 Flat to Bind9 DLZ

On 25/03/15 16:50, VIKAS wrote: > Hi Team, > > Samba Version = 4.2 > > Bind = 9.10 with dlz > > > Not able to to view replication.(samba-tool drs showrepl) > > > [root at dc2]# samba-tool drs showrepl (want to highlight the name which is > using to connect) > > ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to >

yes i realized that there is something wrong with BIND9_FLATFILE while encountering with samba_upgradedns -h which doesn't show BIND9_FLATFILE Any help on*drs repl* not working i think it is pointing to wrong FQDN how do i correct that ? > >/ Not able to to view replication.(samba-tool drs showrepl) > />/ > />/ > />/ [root at dc2

Hi Vikas, > yes i realized that there is something wrong with BIND9_FLATFILE while > encountering with samba_upgradedns -h which doesn't show BIND9_FLATFILE > > Any help on*drs repl* not working i think it is pointing to wrong FQDN > how do i correct that ? >> >/ Not able to to view replication.(samba-tool drs showrepl) >> />/ >> />/ >>

Hi team, I have Samba (4.9.5) AD DC, and when trying to add second DC, join fail: # samba-tool domain join zamecek.home DC -U"SSUPS-ZAMECEK\administrator" --option='idmap_ldb:use rfc2307 = yes' --dns-backend=BIND9_DLZ Finding a writeable DC for domain 'zamecek.home' Found DC dc1.zamecek.home Password for [SSUPS-ZAMECEK\administrator]: workgroup is SSUPS-ZAMECEK realm is

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

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

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, After reading wiki documentation about join I have tested to join a second dc, but with problems. I need to add a second controller to our AD, and then upgrade existing server (4.4.5) and I have tried to join a new DC 4.10.7 to 4.4.5 server but I receive join errors, attached output wit and without debug: I have executed samba-tool dbcheck --cross-ncs all seems OK I have made a test

On my primary Samba AD DC server all work ok when doing online backup, but on my secudary server I have error: ERROR(<type 'exceptions.IndexError'>): uncaught exception - list index out of range ? File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 177, in _run ??? return self.run(*args, **kwargs) ? File

Dne 2019-03-25 16:02, Rowland Penny via samba napsal: > On Mon, 25 Mar 2019 15:12:16 +0100 > franta via samba <samba at lists.samba.org> wrote: > >> Hi team, >> I have Samba (4.9.5) AD DC, and when trying to add second DC, join >> fail: >> >> # samba-tool domain join zamecek.home DC >> -U"SSUPS-ZAMECEK\administrator"

Hi, Just to reiterate an important point, the 'domain backup' command is there to backup your domain information, not your DC. If you still have a working domain, then you can recover any DC by simply rejoining it to the domain. Do not use backup/restore to recover an individual DC. If you want to recover your entire domain (i.e. power off all your DCs and start again from scratch),

So we have two different Samba servers we are trying to connect to what was originally a Windows 2003 AD and was raised to 2008R2 (both Forest and Domain). (We really only need to connect one of them - the one hosting Samba 4.7.6). Any ideas or suggestions are helpful! We've scoured the lists (Rowland - you are amazing), but still not found what is wrong (we think it is probably a config

On Wed, 27 Mar 2019 09:45:18 +0100 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Hai, > > > I dont think one noticed this.. > > ldbsearch -H ldap://dc4 -UAdministrator > ldbsearch -H ldap://dc1 -U Administrator > > So whats the difference when you see this responce of the command: > Invalid option -U: unknown ... >

OK, we're getting closer here I think. I repeated with -d 2 without much help. Here is -d 3, which may point us in the right direction. As I suspected, it seems to point to some corruption in the DNS still, perhaps? The key line seems to be here: Missing parent while attempting to apply records: No parent with GUID 60e25dda-6d35-4aab-bfa5-6137cb271e27 found for object remotely known as

Le 09/07/2015 18:20, Rowland Penny a écrit : > On 09/07/15 17:06, zorg wrote: >> But If i want my samba4 to be dns after when i ll decide to stop the >> other dc >> >> can't i keep the to dns >> >> Could you explain a bit >> >> >> >> Le 09/07/2015 17:55, Marc Muehlfeld a écrit : >>> Hello, >>> >>> Am

Hello, after successfully demoted a samba4 dc node (redhat linux 6.4 with samba v4.1, hostname:samba4dc3) i tried to join another dc to domain (redhat linux 6.4 with samba v4.1, hostname:samba4dc4) and this is what i get: root at samba4dc4 /root #samba-tool domain join samdom.example.com DC -Uadministrator --realm=samdom.example.com --dns-backend=NONE Finding a writeable DC for domain

On Wed, 12 Dec 2018 16:01:52 +0100 "peter.grotz--- via samba" <samba at lists.samba.org> wrote: > Thanks Rowland for your answer. > > these are sernet-packages from their subscription. > > There are 4 DCs (all with last sernet-rpms) 2 are demoted with probs > (dc-01 and dc-02 both centos6) and 2 are running (dc-10 and dc-11 on > centos 7) > >

Hi, I've tried to update my samba AD/DC environment. Then, I've removed a existing offline DC with "samba-tool domain demote --remove-other-dead-server=genos". I've re-created "genos" (yes, I try to keep the same name and IP address) and install a 4.10.2 samba version (I know the new version is 4.11.0). When I've tried to join it on my domain, I've received

On 8 September 2016 at 08:17, Rowland Penny via samba <samba at lists.samba.org > wrote: > On Thu, 08 Sep 2016 12:58:18 +1200 > Andrew Bartlett <abartlet at samba.org> wrote: > > > On Fri, 2016-09-02 at 13:19 +0100, Rowland Penny via samba wrote: > > > > > > > > > I have now found out why you had to provision with samba43, > > > the

> -----Message d'origine----- > De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland > Penny via samba > Envoyé : lundi 21 août 2017 16:34 > À : samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > > On Mon, 21 Aug 2017 15:52:01 +0400 > HB via samba <samba at lists.samba.org> wrote: > > > Hello all,