similar to: Samba4 4.0.3 classicupgrade - Error converting string to value for line: "CurrentVersion"

Hello, I've seen this upgrade error posted before: https://lists.samba.org/archive/samba/2013-January/171022.html but either there is a different issue or I'm misreading the post. Basically when I run the classicupgrade (samba3 to 4) on a test machine, I get the following (the full debug output will be at the end of my post): ....... key added: key=CurrentVersion,key=Windows

Hello, I would try to migrate S3 to S4 in production but these messages (in bold) blocks me to do this. I can authenticate users et computers yet !, So what does they mean ? Regards root at vspdc:~# /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/root/smb3/varlib --dns-backend=BIND9_DLZ --use-xattrs=yes --realm=sc.isc84.org /root/smb3/etc/smb.conf Reading smb.conf

Hello, Indeed when I copied the result for the mailing I made a mistake. MY.DOMAIN is a dummy name. The result of the migration command is Reading smb.conf WARNING: The "idmap backend" option is deprecated WARNING: The "idmap uid" option is deprecated WARNING: The "idmap gid" option is deprecated Provisioning Exporting account policy Exporting groups Severe DB

Hello, I'm upgrading samba3 to samba4 and i've the following error : > /usr/local/samba/bin/samba-tool domain samba3upgrade --dbdir=/root/samba4/samba/ --realm=sc.isc84.org /root/samba4/samba/smb.conf no talloc stackframe around, leaking memory Reading smb.conf Provisioning Exporting account policy Exporting groups *Severe DB error, sambaSamAccount can't miss the samba

Hi. I'm trying to convert from s3 to s4 using classic upgrade. I have LDAP backend and i'm getting this error: Ignoring group 'pgrd' S-1-5-21-511255529-1355219746-1726288727-3007 listed but then not found: Unable to enumerate group members, (-1073741596,NT_STATUS_INTERNAL_DB_CORRUPTION) The problem is that this group is valid and almost all our users are in this group, so i

Hello, I've migrated successfully samba3 to samba4 by using samba-tool. Today, i did "git pull", ran make clean, make and make install and the command : /usr/local/samba/bin/samba-tool domain samba3upgrade --dbdir=/root/samba3/samba/ --realm=sc.isc84.org /root/samba3/etc/smb.conf which gave : no talloc stackframe around, leaking memory You are not root or your system do not

Hello, I realize again test by resuming all 0 with the following configuration and I arrive at the same result. -------------------- smb.conf [global]     netbios name = svdom     server string = Gestionnaire de domaine     workgroup = dom.domain     hosts allow = 192.168.15. 192.168.6. 10.0.7.     security = user     domain master = yes     domain logons = yes     prefered master =

Hi all. We have big problem with adding new machine to our domain. 2 weeks ago we upgrade our machine to Debian 4 (etch). Than we automatic update our samba to version 3.0.24 (from debian package). We use LDAP backend for samba. When we try add Windows XP or Windows 2000 to our domain, we got this error message on client: Security database is corrupted. On server we have in log file log.smbd

Hi, ok, now join(with samba 4.10.6) was ok, but same original error :-/ smbclient //localhost/netlogon -UAdministrator -c 'ls' Enter XXXXXXX\Administrator's password: session setup failed: NT_STATUS_INTERNAL_DB_CORRUPTION Regards; On 24/07/2019 10:17, Rowland penny via samba wrote: > On 24/07/2019 12:53, Carlos via samba wrote: >> HI >> >> As the reported

Hi guys, I'm trying to get the Samba4 multi-master replication to work. I set up the primary domain controller using this howto (under CentOS 6.2 x64): http://wiki.samba.org/index.php/Samba4/HOWTO I installed bind 9.8.3 and enabled encrypted dns updates. I set up another VM with the same CentOS version and oriented myself on this howto:

On Wed, 5 Sep 2018 16:53:50 +0200 Philippe Maladjian via samba <samba at lists.samba.org> wrote: > Hello, > > Indeed when I copied the result for the mailing I made a mistake. > MY.DOMAIN is a dummy name. The result of the migration command is > > Reading smb.conf > WARNING: The "idmap backend" option is deprecated > WARNING: The "idmap uid"

Hi! I am running samba 4.6.16 in Ubuntu 18.04 all ok, after ugrade to Samba 4.10.6, in running test smbclient //localhost/netlogon -UAdministrator -c 'ls' show me erro: NT_STATUS_INTERNAL_DB_CORRUPTION so I demoted dc e and installed 4.6 and upgraded to 8.3 (same versions of my other samba dcs on the network), and all ok again. existe any problem in update dc 4.6 to 4.10 or 4.8 to

Sven, Fist fix the smb.conf as i suggested, cap and non caps where it should be. Resolving settings based on the script output looks ok. Fix krb5.conf Then how many DC's are you having? > So, could somebody maybe help with the NT_STATUS_INTERNAL_DB_CORRUPTION > / DRS replication issue? Or will it be easier to just demote > the DC and provision a new one? Are all DC's

Hello, I have a problem with my samba4 domain cluster: there are 2 machines, - primary and secondary server. Everything was working fine, but i had a hard drive failure on primary PDC, so i reinstalled and restored a backup to it. Aftrwards i saw the warning about never restoring database from backups. Now I have the following problems: users can login and all group policies are provided, but

Hi @ all, we use samba as a fileserver on CentOS and an OpenLDAP server on Ubuntu 10.04. The samba server shared only files, so we can access with the win7 clients (and OpenLDAP credentials) to the files on the linux environment. So after upgrade we don't can connected us to the samba share. I have tested the connection with the tool smbclient "smblcient -L <servername> -U

Hi, i upgrade on a new server samba3 to samba4 with a LDAP Backend. I have followed this HowTO ?http://wiki.samba.org/index.php/Samba4/samba-tool/domain/classicupgrade/HOWTO until de classicupgrade step Here is the errors I get ?/usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/root/samba3/tdbfiles --use-xattrs=yes? --realm=bceao.int /root/samba3/tdbfiles/smb.conf Reading

Le 05/09/2018 à 18:32, Rowland Penny via samba a écrit : > On Wed, 5 Sep 2018 16:53:50 +0200 > Philippe Maladjian via samba <samba at lists.samba.org> wrote: > >> Hello, >> >> Indeed when I copied the result for the mailing I made a mistake. >> MY.DOMAIN is a dummy name. The result of the migration command is >> >> Reading smb.conf >>

dn: cn=Domain Admins,ou=groups,dc=mydomain objectClass: top objectClass: posixGroup objectClass: sambaGroupMapping gidNumber: 512 cn: Domain Admins description: Netbios Domain Administrators sambaSID: S-1-5-21-3936576374-1604348213-1812465911-512 sambaGroupType: 2 displayName: Domain Admins memberUid: root memberUid: sadmin dn: cn=Domain Users,ou=groups,dc=mydomain objectClass: top objectClass:

Hello, I have a question with password never expired flag during changing password. If X flag for password never expired has been set in account flags for a user, password change would cause to lose the X flags. By taking a look at the code of the line 993 in passdb/passdb.c, it said all other acb flags will be inherited from current existing account ctrl bit, except for

Hello, I am working on the migration of our samba 3.5 domain controller (redhat 5.7) with ldap backend to samba 4.5 on a new server (debian 9.5). On the new server I transferred the smb.conf and all the contents of the /var/lib/samba folder to a temporary folder /root/samba3. To start the migration I use the command: # samba-tool domain samba3upgrade --dbdir =/root/samba3/ --realm =