similar to: error when samba-tool domain classicupgrade

Migration was held in connection with the breakdown of the old server after setting up a new server stopped working to add windows pc to a domain root at pdc:/var/log/samba# cat /etc/samba/smb.conf [global] # Default options allow nt4 crypto = yes client ntlmv2 auth = no disable spoolss = yes dns proxy

hi It can be so help [global] >---admin users = @nt_admins if not then I need 1. root at pdc:~# testparm 2. root at pdc:~# ldapsearch -xLLL -H ldapi:/// -b ou=groups,ou=arkhangelsk,dc=rugion,dc=ru ldap suffix = ou=arkhangelsk,dc=rugion,dc=ru ldap group suffix = ou=groups 3. try log level = 10 max log size = 1000 and go through the authorization in windows pc

hi all I have two different Samba versions as PDC and BDC and depending on which one is "domain master" users which are domain admins are not recognized as such. Everything seems normal with 3.6.23-25.el6_7 as "domain master" but when I configure them so 4.2.10 is the master then I login to Win7 fine but Windows tells me that the user is not an Admin and I need to supply

On 11.10.2016 17:22, Harry Jede via samba wrote: > Am Dienstag, 11. Oktober 2016 schrieben Sie: >> On 11.10.2016 13:52, Harry Jede via samba wrote: >>> On 10:43:49 wrote Gavrilov Aleksey via samba: >>> Until now, you have destroyed your domain. >>> Is the ldap directory on localhost in production or is this pc in a >>> test lab? >> a copy of the

On 10:43:49 wrote Gavrilov Aleksey via samba: > Migration was held in connection with the breakdown of the old server > after setting up a new server stopped working to add windows pc to a > domain > > root at pdc:/var/log/samba# cat /etc/samba/smb.conf > > [global] > # Default options > allow nt4 crypto = yes > client ntlmv2

On Mon, 10 Oct 2016 17:42:54 +0500 Gavrilov Aleksey via samba <samba at lists.samba.org> wrote: > Migration was held in connection with the breakdown of the old server > after setting up a new server stopped working to add windows pc to a > domain > > root at pdc:/var/log/samba# cat /etc/samba/smb.conf > > [global] > # Default options > allow

Am Mittwoch, 12. Oktober 2016 schrieben Sie: > Thanks to your help, earned. > > 1. I reinstalled ldap > > 2. remove all entries except sambaDomainName According to your logs, you have had three entries > 2. smbldap-populate > > 3. /usr/local/sbin/smbldap-passwd -s root > > 4. net rpc join -S 127.0.0.1 -U root%secret > > 5. restore from a backup of users,

Same as on the squid keytab file : chown root:squid /etc/squid3/ldappass.txt chmod 440 /etc/squid3/ldappass.txt Greetz, > -----Oorspronkelijk bericht----- > Van: squid-users [mailto:squid-users-bounces at lists.squid-cache.org] Namens > alesironi > Verzonden: maandag 1 februari 2016 13:28 > Aan: squid-users at lists.squid-cache.org > Onderwerp: Re: [squid-users]

Am Dienstag, 11. Oktober 2016 schrieben Sie: > On 11.10.2016 13:52, Harry Jede via samba wrote: > > On 10:43:49 wrote Gavrilov Aleksey via samba: > > Until now, you have destroyed your domain. > > Is the ldap directory on localhost in production or is this pc in a > > test lab? > > a copy of the old server ldap > > >> How do I introduce a new PDC in a

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

I used to upgrade samba3 to samba4 with almost successful with one problem, administrator can't access. As administrator, by default it is the only user account that is given full control over the system. My query is how to change the administrator password? we have one account which can join to the samba 4 AD based on the migrated data but the problem can't change the administrator or

How do we check the data from Samba4 that the data from Samba3 successfully migrated? I dunno if it successfully migrated coz got these (last part): [root at gaara LiveData]# /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/srv/LiveData/var_lib_samba/samba --use-xattrs=yes --realm=kazekage.sura.sandbox.local --dns-backend=SAMBA_INTERNAL /srv/smb.conf Once the above files are

Rowland penny wrote on 3/18/16 12:58 PM: > On 18/03/16 19:27, Robert Moulton wrote: >> Rowland penny wrote on 3/18/16 11:48 AM: >>> On 18/03/16 18:19, Robert Moulton wrote: >>>> Greetings - On our samba 4 (4.3.3) AD controller I just noticed >>>> something odd. When I run 'samba-tool fsmo show' I get an error: >>>> >>>> #

Rowland Penny via samba писал 2018-09-03 17:12: > On Mon, 03 Sep 2018 04:27:07 +0000 > "Konstantin Boyandin \(lists\) via samba" <samba at lists.samba.org> > wrote: > >> Hello, >> >> Going further with migrating NT4 domain (Samba 3) to Samba 4. Thanks >> for the previous suggestions. >> >> When doing >> >> #

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 >

Hi, we might have encountered a possible python 3 bug in samba 4.11. We are using the sernet-samba packages. While the classicupgrade works on centos6 (using python 2) it fails on centos8 (using python3) with a classic python3 bug message: # samba-tool domain classicupgrade --dbdir=pdc-files/ --realm=ad.xxx.de --dns-backend=SAMBA_INTERNAL pdc-files/smb.conf INFO 2019-09-25 06:15:34,366 pid:12017

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

Testing this "classic upgrade" scenario on a test server and have some issues. I'm using the Sernet 4.2.1 packages on Debian Wheezy. I copied the required tdb files and the smb.conf to the new test server (named WHEEZY). Edited the smb.conf to reflect the new host/netbios name of WHEEZY (remember that I want to keep the old PDC in service afterword for file and print sharing duties

Rowland penny wrote on 3/18/16 11:48 AM: > On 18/03/16 18:19, Robert Moulton wrote: >> Greetings - On our samba 4 (4.3.3) AD controller I just noticed >> something odd. When I run 'samba-tool fsmo show' I get an error: >> >> # samba-tool fsmo show >> ERROR(ldb): uncaught exception - No such Base DN: >>

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