search for: ting_active_directori

Forgot this one. systemctl edit bind9 #/etc/systemd/system/bind9.service.d/override.conf is created. # add below. [Service] # Disable reloading completely. ExecReload= # Or set it to restart #ExecReload=/usr/sbin/rndc restart Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > L.P.H. van Belle via samba >

I only see one error here. Debian 9.6 .. Update to 9.7 ;-) :-P Because of : https://www.debian.org/security/2019/dsa-4371 Looks good Stefan. It the preseed on github still the same? Working at things here also. .. Bit to much things but ok. Fun things :-) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens >

I am working towards joining my second DC to the first. If I am understanding: https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory correctly I am to get bind9 working properly before the join should happen. I am getting this: > root at dc2:~# systemctl status bind9 > > ? bind9.service - BIND Domain Name Server > > Loaded: loaded

Il 29/11/2018 15:22, Rowland Penny via samba ha scritto: > On Thu, 29 Nov 2018 15:03:03 +0100 > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > >> You dns keytab looks strange, my be due to manual changes.. > It looks strange because there is one of these missing: > > 1 DNS/mysamba4dc.mydomain.com at MYDOMAIN.COM > > Could be cut &

Hai Stephan, You need also this in smb.conf # enable offline logins winbind offline logon = yes I did also test my logins with one DC turned off. And login on the DM is no problem or my pcs, no problem. I did not test the AD logins thats because these have only linux logins for maintainance. And that always works. In a 2 DC setup, setup your nameservers first to the LAN ip of the

greetings, samba-users, I am currently preparing to join a second Samba-DC to a Samba-based ADS. DC1 is a debian-9.6 machine, running samba-4.8.8 from Louis' repos. DC2 is basically identically set up (thank you, ansible) and I read and followed (1) so far, except the actual join. sysvol-rsync, kerberos ticket, modified smb.conf, resolv.conf ... done I assume 4.8.8 will give me no

I added a 2nd DC (ADC2) to a samba-ADS today. debian-9.3, samba-4.6.11 from Louis followed https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory replication works afai see - We wanted to test services after turning off the first DC, and running ADC2 and a DM file-server only. DC1/backup: 10.0.0.224 ADC2: 10.0.0.230 We then get NT_STATUS_NO_LOGON_SERVERS On the

; TSIG error with server: tsig verify failure Mayabe update/setup your TSIG key. https://access.redhat.com/documentation/en-us/openshift_enterprise/2/html/puppet_deployment_guide/generating_a_bind_tsig_key Im also wondering why RH is using : '--disable-isc-spnego' Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org]

> So you never read this: > https://wiki.samba.org/index.php/Changing_the_DNS_Back_End_of_a_Samba_AD_DC > Which means that you probably never ran the aptly named > 'samba_upgradedns'Of course I ran this. Many times. I'm not stupid, Rowland. At least I can read:D If I've seen that Bind doesn't work, I had to change backend to internal DNS.I carefully read and made