similar to: Samba 3.6 to 4.1 problem with classicupgrade

Hello, I'm running a Samba 4.3.3 install on FreeBSD 8.4 (ZFS) in domain mode with passdb tdb backend. The databases and config files are the current versions of an install that I think started in the 1.9.x version range back in the late 90s (I can't remember exactly--it's been a long time!) and smbpasswd days. I'm now trying to convert to an AD install using the classicupgrade

On 19/03/16 17:16, Sonic wrote: > On Fri, Mar 18, 2016 at 4:04 PM, Andrew Bartlett <abartlet at samba.org> wrote: >> The upgrade code assumes you run on the same host. I realise now that >> folks doing an upgrade use that an an opportunity to upgrade hardware, >> and keep old systems as fallbacks, so the assumptions cause trouble. >> >> Make the new host

On Fri, Mar 18, 2016 at 4:04 PM, Andrew Bartlett <abartlet at samba.org> wrote: > The upgrade code assumes you run on the same host. I realise now that > folks doing an upgrade use that an an opportunity to upgrade hardware, > and keep old systems as fallbacks, so the assumptions cause trouble. > > Make the new host identical in terms of the data needed to upgrade >

We're evaluating joining another samba domain controller in read-only mode. With a default provisioning, when running the samba-tool domain RODC, it fails with the following error: ldb: ldb_trace_request: (tdb)->search ldb: ldb_asprintf/set_errstring: NULL Base DN invalid for a base search ldb_wrap open of hklm.ldb ldb: start ldb transaction (nesting: 0) ldb: ldb_trace_request:

Perhaps I'm rooting around at a lower level than I should be, and somewhat beyond what I can understand, but here is a bit of info I dug up. It might be helpful? The GUID in the first search matches the one referred to in the error message. $ sudo ldbsearch -H /var/lib/samba/private/sam.ldb.d/DC\=DOMAINDNSZONES\,DC\=REDACTED\,DC\=DOMAIN\,DC\=LOCAL.ldb "(DC=DomainDnsZones)" # record

Tested again to join, now clearing both Kerberos, Samba config and Samba private folder. The new log now has some more details (resolve_lmhosts: Attempting lmhosts lookup for name SRVAD-OLD.SAMDOM.LOCAL<0x20>), but I'm still not able to join. Wonder why is it trying to do an lmhosts lookup, 4.6 is not. An identical server (with same hostname and IP) with Samba 4.6 joins without

On 30.08.19 11:01, Andrew Bartlett wrote: > I'm very sorry to advise that this script is not race-free in the > locking done on the AD databases, which is why we have written the > 'samba-tool domain backup offline' tool which holds the correct locks. > > You should only need to back up the domain on one DC as long as you are > confident the DC is correctly

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

Tested again to join, now clearing both Kerberos, Samba config and Samba private folder. The new log now has some more details (resolve_lmhosts: Attempting lmhosts lookup for name SRVAD-OLD.SAMDOM.LOCAL<0x20>), but I'm still not able to join. Wonder why is it trying to do an lmhosts lookup, 4.6 is not. An identical server (with same hostname and IP) with Samba 4.6 joins without

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

It seems I'm talking to myself... anyway another test here: Added the existing DC IP config to /etc/hosts and the join now shows a more explicit LDAP error: --- Wrong username or password: kinit for SRVAD-NEW$@SAMDOM.LOCAL failed (Preauthentication failed) SPNEGO(gssapi_krb5) creating NEG_TOKEN_INIT for ldap/SRVAD-OLD.SAMDOM.LOCAL failed (next[ntlmssp]): NT_STATUS_LOGON_FAILURE Got

Hi all, I have a problem during classic-upgrade : Importing groups Group already exists sid=S-1-5-21-4023731279-819928261-1073345436-512, groupname=Domain Admins existing_groupname=Domain Admins, Ignoring. Group already exists sid=S-1-5-21-4023731279-819928261-1073345436-514, groupname=Domain Guest existing_groupname=Domain Guests, Ignoring. Group already exists

On 07/03/16 19:04, Sonic wrote: > Sorry for the long post but attempted this several over the past year > with no success but staying on an NT4 domain is no longer viable. Need > to get this resolved so hopefully there will be a clue somewhere in > this montage. > > The current PDC is samba-3.6.25 running on Gentoo using tdbsam backend. > The new AD will be a Debian LXC

Hello, I'm testing samba4. I've setup a small samba3+ldap pdc, and then I tried a classicupgrade, but I can't pass step 4 of the howto. ubuntu at samba4:~/samba4$ /usr/local/samba/sbin/samba -V Version 4.1.0pre1-GIT-899cdc4 ubuntu at samba4:~/samba4$ sudo /usr/local/samba/bin/samba-tool domain classicupgrade --realm=example.com --dbdir=/root/samba /root/samba/smb.conf Reading

On Fri, Mar 18, 2016 at 2:39 PM, Andrew Bartlett <abartlet at samba.org> wrote: > Exactly. Think about it a little - how can it determine the group > membership, if the users/groups do not exist locally on the host doing > the migration? To clarify then: Do I need both the users and groups on the new host as they are on the old host, or just the groups? Is there any constraint

Sorry for the long post but attempted this several over the past year with no success but staying on an NT4 domain is no longer viable. Need to get this resolved so hopefully there will be a clue somewhere in this montage. The current PDC is samba-3.6.25 running on Gentoo using tdbsam backend. The new AD will be a Debian LXC container running on Debian Jessie using samba compiled from git

Hi, I'm trying to migrate a NT4 domain under Samba3 to an AD DC under Samba4 on a separate server. During the classicupgrade, there were a number warnings while importing groups: WARNING 2019-05-13 15:09:56,728 pid:25284 /usr/local/samba/lib64/python2.7/site-packages/samba/upgrade.py #299: Could not add group name=Domain Admins ((68, 'Entry CN=Domain

Hi I am running the "samba-tool domain classicupgrade", and after solving some problems (thread http://lists.samba.org/archive/samba/2013-January/170777.html), now I am getting this error: # samba-tool domain classicupgrade --dbdir ~/sambav3 --realm XXXXXX.YYYYYY.TEST --use-xattrs=yes ~/sambav3/smb.conf -d9 ... init_sam_from_ldap: Entry found for user: XXXXXX init_sam_from_ldap: Entry

Rowland Penny via samba <samba at lists.samba.org> writes: > On Thu, 22 Mar 2018 10:50:35 +0700 > Olivier via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> I am progressing slowly with the migration from Samba3 to Samba4. >> >> I have escaped the bug 13060, now I get to: >> >> Adding groups >> Importing groups

I have a new server running CentOS 6.4 x64, which will serve as our new Samba4 server. It is set up in a test environment, and I've copied over the tdb files and the smb.conf file from our samba3 server (Same OS and version). I'm trying to do an in-place upgrade on the copied files, but keep hitting an assert / uncaught exception during the upgrade: # /usr/local/samba/bin/samba-tool