similar to: Samba fsmo/demote/unjoin trouble after crash

Hello samba team ! As you know https://lists.samba.org/archive/samba/2017-June/209112.html during the upgrade from Debian Jessie to Debian Stretch all my three DCs have lost their machine password. Or something is corrupted in the machine password database. So the DRS stopped working. To try to repair safely the issue I have virtualised the three machines. Here what I have tried : -> the

I have transferred all fsmo's except domain and forest.? When I attempt either one of these I get this error: samba-tool fsmo transfer --role=forestdns ERROR: Failed to delete role 'forestdns': LDAP error 50 LDAP_INSUFFICIENT_ACCESS_RIGHTS -? <00002098: SecErr: DSID-03151D80, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0 > <> Any ideas on how to overcome this? -- Bob

Hello, I would like to rename my w3k AD domain (I am fine with this process) - one thing that worries me is how the samba 3.0.3pre2 Suse 9.0 server will handle it. Should I delete the computer account from AD? Is there an unjoin/rejoin domain procedure for samba? For the domain name change to work, the AD needs to be in native mode, can anyone see any problems with samba switching from mixed

On 07/19/2019 03:08 PM, Rowland penny via samba wrote: > On 19/07/2019 20:41, Robert A Wooldridge via samba wrote: >> I have transferred all fsmo's except domain and forest.? When I >> attempt either one of these I get this error: >> >> samba-tool fsmo transfer --role=forestdns >> ERROR: Failed to delete role 'forestdns': LDAP error 50 >>

Hi, I followed the tutorial below to do backup of the Samba4: https://wiki.samba.org/index.php/Backup_and_Recovery When I execute the backup script manually, it is executed perfectly, but when I execute in the crontab, it isn't work. It is my crontab on Debian 7: 0 1 * * 1-5 /usr/sbin/samba_backup Does somebody have an idea ? Regards, Márcio

Hi list, We use samba 4.1.17 (debian's version) on several DCs. I just realized that one of them is desynced and cannot get it to resync. The long story: we got 5 DCs splitted over several sites. Recently we had to replace one of them (let's call him DC5). Since both had to run in parallel for data recovery/users work we decided to join a brand new DC (DC6) and latter demote the

the script is not complete. It isnt stopping samba and as the wiki says, DONT backup a running samba. Greetz, Louis >-----Oorspronkelijk bericht----- >Van: samba [mailto:samba-bounces at lists.samba.org] Namens >Giuseppe Arvati >Verzonden: vrijdag 21 augustus 2015 11:25 >Aan: Marc Muehlfeld; Marcio Demetrio Bacci; samba at lists.samba.org >Onderwerp: Re: [Samba] Problem

On 01/04/16 22:38, spindles7 wrote: > Hi Rowland, > Have tried your patch, and now the Demote succeeds: > > root at dc3:~# samba-tool domain demote -Uadministrator > Using dc1.microlynx.com as partner server for the demotion > Password for [MICROLYNX\administrator]: > Deactivating inbound replication > Asking partner server dc1.microlynx.com to synchronize from us >

Yes they are, see samba-tool drs replicate -h. Am 24.02.2016 um 16:24 schrieb Achim Gottinger: > Have you tried to replicate with the --sync-forced and --full-sync > options? > > Am 24.02.2016 um 14:31 schrieb Sébastien Le Ray: >> Hi list, >> >> We use samba 4.1.17 (debian's version) on several DCs. I just >> realized that one of them is desynced and

Hi Rowland, Have tried your patch, and now the Demote succeeds: root at dc3:~# samba-tool domain demote -Uadministrator Using dc1.microlynx.com as partner server for the demotion Password for [MICROLYNX\administrator]: Deactivating inbound replication Asking partner server dc1.microlynx.com to synchronize from us Changing userControl and container Removing Sysvol reference:

----- On Apr 23, 2019, at 11:34 AM, samba samba at lists.samba.org wrote: > On Tue, 23 Apr 2019 11:11:21 -0500 (CDT) > Mike Ray via samba <samba at lists.samba.org> wrote: > >> About a week and half ago I upgraded from 4.0.12 to 4.9.6. Overall, >> things are functioning. >> >> However, I have come across several strange behaviors and wandered if >>

Thanks Rowland. Have submitted a bug report (No 11818). spindles7 On Thu, 31 Mar 2016 09:38:02 +0100, Rowland penny <rpenny at samba.org> wrote: >On 30/03/16 23:26, spindles7 wrote: >> Hi all, >> I am consistently getting the error: >> >> root at dc2:~# samba-tool domain demote -Uadministrator >> Using dc1.microlynx.com as partner server for the demotion

Hi, Back in the samba 4.1 days, we experienced a samba database corruption: tombstones not being deleted from sam.lbd, ultimately resulting in a huge database, full root disk, samba crashing, we were completely down. We asked the great guys at sernet to help, they did super work, and managed to get us up and running again, including the addition of a fresh DC4. Currently on 4.5.15, we have

a quick read and one thing, the dc4, after the upgrade to 4.7, did you reindex the ad database? if im correct, samba-tool dbcheck — reindex i did read that from a list somewere, a responce of andrew. greetz Louis (mobile) Op 23 okt. 2017 om 20:47 heeft mj via samba <samba at lists.samba.org> het volgende geschreven: Hi, Back in the samba 4.1 days, we experienced a samba database

About a week and half ago I upgraded from 4.0.12 to 4.9.6. Overall, things are functioning. However, I have come across several strange behaviors and wandered if anyone else has noticed similar behavior on 4.9.6 or has any suggestions of what might be occurring. As background information, I have 3 DCs (dc3, dc4 and dc5) -- all running the same version (4.9.6) and all have the same configuration;

Thanks for the answer. > Did you got errors during the classicupgrade? I didn't do classicupgrade. My Samba AD DC was installed from scratch some months ago using the instructions from this page https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO and everything had been working well. I just upgraded some deb-packages with samba to the same version but different buid-release. Regarding

On Tue, 23 Apr 2019 11:11:21 -0500 (CDT) Mike Ray via samba <samba at lists.samba.org> wrote: > About a week and half ago I upgraded from 4.0.12 to 4.9.6. Overall, > things are functioning. > > However, I have come across several strange behaviors and wandered if > anyone else has noticed similar behavior on 4.9.6 or has any > suggestions of what might be occurring. >

All- I've got 3 DCs (version 4.9.6-12) that, prior to today, were running without issue (as best I could tell). Every night I run a few commands to monitor the status of the DCs/domain. I run: * dbcheck --cross-ncs * samba-tool drs kcc <other DCs> * samba-tool ldapcmp <local DC> <other DCs> (domain|configuration|schema|dnsdomain|dnsforest) * samba-tool drs showrepl These

----- On May 22, 2019, at 10:01 AM, samba samba at lists.samba.org wrote: > Try again with : > > samba-tool ldapcmp dc5.$(hostname -d) dc3.$(hostname -d) DNSFOREST > As in dc5.your.dns.domain.tld ... > > Whats the result.? The failure is still present -- no change in the output of the command: # samba-tool ldapcmp dc3.domain.local dc5.domain.local DNSFOREST ERROR(ldb):

Hello, (samba 4.0.8 compiled from git source) Just tried the samba_backup from https://wiki.samba.org/index.php/Backup_and_Recovery line 54 mention : tdbbackup $ldb where it should be /usr/local/samba/bin/tdbbackup $ldb Thanks for this nice samba version ! electronico