similar to: Ubdate Samba 4 from 4.1.11 to 4.9.3

Join new DC (from virtual machine) https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory (or 2. from 2 vm!) with bind/dhcp/.. Then demote old DC https://wiki.samba.org/index.php/Demoting_a_Samba_AD_DC and install (clean) 4.9.3, then join it again, demote vm,.. 01.12.2018 0:40, Igor Sousa via samba пишет: > I've tried use samba-tool domain backup, but the

Hi Rowland, Thanks for your reply. I'm using Samba 4.10.2 compiled from source. -- Igor Sousa Em qua, 17 de abr de 2019 às 10:21, Rowland Penny via samba < samba at lists.samba.org> escreveu: > On Wed, 17 Apr 2019 10:08:21 -0300 > Igor Sousa via samba <samba at lists.samba.org> wrote: > > > Hi everyone, > > > > I have a question: is possible use

Hi Nico, I've understood about use export PYTHON=python3.4 in /etc/profile. The host that I've done it is in my test environment. I have only question about this: after samba 4.10.2 installed, it ever never need use python3 to do anything about samba? PS1: In my environment, the host run only Samba (samba and bind) service. I disagree about use python 3.6 instead python 3.4, though. In

I'm sorry to I forgot answer appropriate. I'm running CentOS 7 with all packages upgraded. I've followed instruction in https://wiki.samba.org/index.php/Package_Dependencies_Required_to_Build_Samba with some need modifications (yum line is bellow this text) and I've installed python 3.4. I've installed Bind9 from package manager where Bind9 version is 9.9.4. YUM command to

Hi Gabriel, I've compiled Samba 4.10.2 on CentOS 7 successfully. I've read the wiki that 4.10.2 version is full compatible with python 3, specifically python 3.4. Then I've install, use the yum command, the package python34-devel and I've added an environment variable at /etc/profile with export PYTHON=python3.4. Thus, I've run ./configure, make and make install with no

Hi, Rowland, I've complied samba use: ./configure --enable-debug --enable-selftest --with-systemd make make install I haven't done anything to install MIT Kerberos and I've followed wiki to install Samba with your default Kerberos. Then I believe that I use Heimdal Kerberos I've installed EPEL repository to install python3 and other dependencies such as python36-dns. I can run

Rowland, I've done almost all permissions change, I forgot bind-dns directory. Now, the named service still doesn't start and journalctl -xe showed me that this occurs because permission denied to run dlz_bind9_9.so. I've checked out and the lib and directory /usr/local/samba/lib/bind9/ have execute permission to named group. The output of ls command, journalctl -xe and

Hi Rowland, Thank you for your explanation. Do you think that I should recompile source with ./configure only? I don't have /usr/sbin/samba file. The $PATH and /usr/local/samba/etc/smb.conf content follow below. [root at king ~]# echo $PATH /usr/local/samba/bin/:/usr/local/samba/sbin/:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin [root at king ~]# cat

Rowland, My configure line is ./configure --enable-debug --enable-selftest --with-systemd. A hour ago, I ignored the inconsistency that I reported in the first e-mail of this topic and I proceeded as described at topic "Joining a Samba DC to an Existing Active Directory" and I joined new DC with command: samba-tool domain join mydomain.com DC -U"MYDOMAIN\administrator"

Hi, I have a question about samba 4 with systemd. I've followed the "Managing the Samba AD DC Service Using Systemd" and I've created /etc/systemd/system/samba-ad-dc.service file with the following content: [Unit] Description=Samba Active Directory Domain Controller After=network.target remote-fs.target nss-lookup.target [Service] Type=forking

Rowland, I was thinking if I did anything wrong, but your clarification cleared my mind. I appreciate your help. I'm waiting if other person had a same issue and solved it. Thanks a lot for your help, Igor Sousa On Fri, Apr 26, 2019, 13:26 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Fri, 26 Apr 2019 13:02:07 -0300 > Igor Sousa <igorvolt at gmail.com>

Em seg, 12 de ago de 2019 ?s 14:36, Rowland penny via samba < samba at lists.samba.org> escreveu: > > OOOOOPPPPSSSS > > > > You have compiled Samba yourself, so samba_dnsupdate will not be in > > /usr/sbin, it will be in /usr/local/samba/sbin > > > > so change the line in smb.conf to: > > > > dns update command =

Hi everyone, I have a question: is possible use BIND9 as DNS backend on a new Samba DC that will join into a domain where there are Samba DCs are using Samba Internal DNS server? I know that is a trivial question for someone, but I've followed steps described on wiki's topic "Joining a Samba DC to an Existing Active Directory" and in "Preparing the Host for Joining the

Thanks Gabben and Andrew. I've understood but a new question emerged: Each DC server on my domain has a different pair cert/key and a different CA cert after deployment, correct? If so, is it a best practice to generate new cert for each DC server and sign them with a unique CA? OBS: Every DC servers belongs to the same domain. -- Igor Sousa Em dom., 14 de jun. de 2020 ?s 16:46, Andrew

Hi Louis, I've modify my /etc/systemd/system/samba-ad-dc file following your advice, I only changed bind9.service to named.service (I've run samba on CentOS 7 with Bind9_DLZ). I've checked again if there are others smbd, nmbd, winbindd an samba services on systemd, but they there aren't. The samba-ad-dc service still to fail when I've tried stop it. I've installed samba

Hi Rowland, My domain is a Samba Domain originally. I don't have any Windows DC and I've never had a Windows DC in this domain, only Windows members. My master DC is too old samba version and I've put a new DC with samba 4.10.2 and I've tried to update a secondary DC that had had offline. Then I have demonted it and compile a Samba 4.10.2 and I've tried to join it with the

Hi everyone, I have a question about certificates generated on Samba AD/DC deployment. After all server configuration, I notice that there are ca.pem, cert.pem and key.pem on /usr/local/samba/private/tls directory. I realize the ca.pem and cert.pem have 2 years validity. Will Samba AD/DC generate automatically new certs before this time over? Or, must I have to generate them manually? -- Igor

Em sex, 9 de ago de 2019 ?s 17:26, Rowland penny via samba < samba at lists.samba.org> escreveu: > Well it shouldn't ;-) > > Each DC should use itself for its nameserver > Ok. I understand and I think I've forgotten any step when I had mounted 'king'. My bad! I've set 'king' IP as the only namesever on resolv.conf and I've got a new Kerberos

The master DC runs on Debian 7 and samba 4.1.10. I know this is bad because both versions are too old, but I'm trying to resolve it with upgrade my secondaries DC's. The DC that has failed to join this domain runs on CentOS7, kernel release 3.10.0-1062.1.2.el7.x86_64, and samba 4.10.2. I have a friend that know so much about MS solutions (he has MS certificate) and he has asked me if

On 13/08/2019 21:28, Igor Sousa wrote: > I've found divergences when I've compared the dns entries on 'king' > and 'samba4' servers ('samba4' has the fsmo roles on 'SMB' domain). > There are some 'samba4bkp' entries on 'king' and theses same entries > there aren't on 'samba4'. I've understood that I've could