similar to: samba 4.1.17 upgrade 4.2.x ( sernet) upgrades.. fail...

Hai, Ok, i found the problem of first post below. I did a clean install of 4.1.17 (sernet samba) and installed 2 DC's. The sernet package 4.1.17 for debian wheezy has a bug.. maybe others also, beware. When joining as an extra DC, we are (still) missing the rights on /var/lib/samba/private/dns.keytab after joining the domain. /var/lib/samba/private/dns.keytab is set to root:root 600

Hello Louis, Am 24.04.2015 um 17:16 schrieb L.P.H. van Belle: > Hai.. > > Just tested an upgrade of 4.1.17 to 4.2.1 > result... Fail.. > > setup, > Debian wheezy, sernet samba packages. > 2 clean installed DC's and 1 windows 7 pc joined. > resolv.conf setup > DC1 : namserver DC2 then DC1. > DC2: namserver DC1 then DC2. > > stopped samba on both

hai, ? I just noticed, after my pc woke up my A record disapearred. of my 64bit windows. ? ? Mar? 5 15:43:13 rtd-dc1 named[3717]: samba_dlz: starting transaction on zone INTERNAL.DOMAIN.TLD Mar? 5 15:43:13 rtd-dc1 named[3717]: client 10.249.250.64#49271: update 'INTERNAL.DOMAIN.TLD/IN' denied Mar? 5 15:43:13 rtd-dc1 named[3717]: samba_dlz: cancelling transaction on zone

Hai,   Seeing : > Jan 23 14:55:40 samba01 named[3279]: samba_dlz: configured writeable > zone '168.192.in-addr.arpa' > Jan 23 14:55:40 samba01 named[3279]: zone local.laurenz.ws/NONE: has no > NS records > Jan 23 14:55:40 samba01 named[3279]: samba_dlz: Failed to configure zone > 'local.laurenz.ws'   Normaly you should see first the local.laurenz.ws

Hello, I'm currently running a test setup with Samba4 internal DNS (Version 4.1.5 from Debian backports) and 2 clients (Linux and a Windows). Everything seems to work so far. However, I do not manage to get automatic PTR generation working. I'm using the internal DNS at the moment, but I wouldn't mind changing to bind if this will make it work. While reverse DNS seem to work with

I suspect a zone overlap. Did you add an extra zone manualy in bind? Or something like this... You added : Zone1.Domain.TLD and then Domain.TLD But then with the reverse zones. Because this : > Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-addr.arpa/NONE: > has no NS records Does not look likes the samba_DLZ log lines but a pure bind log line. Review you bind config and

i will do so.... thanks Am 25.01.2017 um 08:46 schrieb L.P.H. van Belle via samba: > Still > > Check this line from you named config. > > include "/etc/bind/named.conf.default-zones"; > > This can cause an overlap in the zones, so be carefull with that one. > > > Greetz, > > Louis > > >> -----Oorspronkelijk bericht----- >> Van: samba

Hai, ? I have automated the install of my member server. Followed the wiki : https://wiki.samba.org/index.php/Samba/Domain_Member? ? Everything works nicely, but...?.. read on..? ;-) ? ok, so wiki says: https://wiki.samba.org/index.php/Setup_and_configure_file_shares? ? and now im at the point : SeDiskOperatorPrivilege and .. for the DC's installed this worked without problems... ? but

Hai, ? Im try to get my id for administrator groups on both server the same. ? with?4.1.17 the solution was simple.. we stop samba on both servers. scp /var/lib/samba/private/idmap.ldb root at 192.168.0.2:/var/lib/samba/private/ ? started samba, and the id's where the same. ? Im using winbindd now with samba 4.2.1 but... ? DC1:? id administrator uid=0(root) gid=100(users)

Hai, ? Im working on my dhcp server + dns setup with samba4.? ? i've exported the?keytabs ? samba-tool domain exportkeytab?/home/krb5.keytab.samba4 ? when i read the contents of this keytab ? ktutil rkt /home/krb5.keytab.samba4 list ?? 1??? 1???????????? RTD-DC1$@INTERNAL.DOMAIN.TLD ?? 2??? 1???????????? RTD-DC1$@INTERNAL.DOMAIN.TLD ?? 3??? 1???????????? RTD-DC1$@INTERNAL.DOMAIN.TLD ??

Hai, cat "/var/lib/samba/private/named.conf" also please. And check if the correct bind9_dlz is enabled. dpkg -l | grep bind9 Jessie, should be 9.9 Stretch should be 9.10 If this server was upgraded then you need to manualy adjust the file above. Looks to my bind9-dlz is enable in smb.conf but not loaded. cat /var/log/daemon.log | grep dlz You should see thing like: samba_dlz:

Mandi! Rowland Penny via samba In chel di` si favelave... > This is probably where you are going wrong. AD lives and dies on DNS, > your DC MUST be authoritative for the AD domain. ...but *is* authoritative! Simply DHCP server assign the ''old'' DNS, where all resolution fr the AD (sub)domain are forwarded to AD DNS... > Your AD clients should be using the DC as

(please reply to the list) If the record does not exist, then you have an other problem. Because samba does support this : cat /var/lib/samba/private/named.conf.update /* this file is auto-generated - do not edit */ update-policy { grant INTERNAL.DOMAIN.TLD ms-self * A AAAA; grant Administrator at INTERNAL.DOMAIN.TLD wildcard * A AAAA SRV CNAME; grant

On 06/08/2019 16:21, L.P.H. van Belle via samba wrote: > Its pretty clear how in the wiki. > > https://wiki.samba.org/index.php/DNS_Administration > > samba-tool dns zonecreate <Your-AD-DNS-Server-IP-or-hostname> 0.99.10.in-addr.arpa > > ;-) And that would get you a /24 network And I also thought wrong, yes the name is wrong, but it should have been '11.0'

Hai Santiago,   Your welkom, i hope i can help you out.   Post my your bind9 configuration, you can anonimize it if needed, but dont remove any lines from it.   And i need a snap of the log when bind is starting up. Like this one : Mar 29 16:42:58 dc1 named[21921]: starting BIND 9.9.5-9+deb8u10-Debian -f -u bind Mar 29 16:42:58 dc1 named[21921]: built with '?pr.... etc. .  Mar

Louis, Upgraded to 4.13 and running "samba-check-db-repl.sh" exits with: "No Samba NT DOMAIN Name found exitting now...: Complete output: > #!/bin/bash -v > > ## > ## Version : 1.0.8 > ## release d.d. : 24-03-2015 > ## Author : L. van Belle > ## E-mail : louis at van-belle.nl > ## Copyright : Free as free can be, copy it, change it if

Hi, I have 2 domain controllers with samba4, and i realized i have some missing spns for the second domain controller: > samba-tool spn list dc1$ dc1$ User CN=dc1,OU=Domain Controllers,DC=test,DC=pt has the following servicePrincipalName: ?? ? HOST/dc1.test.pt ?? ? HOST/dc1.test.pt/test[1] ?? ? ldap/dc1.test.pt/test[1] ?? ? GC/dc1.test.pt/test.pt[2] ?? ?

Yes, offcourse, the 172.19 is a "bad" example. I suggest we use the official RFC 1918 zones. 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 And for example 192.168.0.0/24 as extra, or people get confused. ;-) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden: woensdag 7

>> what is in '/usr/bin/dhcpd-update-samba-dns.sh' ? # will receive addresses from this DHCP server. Instructions are found here: # https://wiki.archlinux.org/index.php/Samba_4_Active_Directory_Domain_Controller#DHCP sleep 5 checkvalues() { [ -z "${2}" ] && echo "Error: argument '${1}' requires a parameter." && exit 1 case ${2} in -*) echo

Hai,   Environment, Debian Jessie.     I got reports about pc's unable to login into the samba ad dc domain. The trust between this workstation and the primary domain failed. This happend on a win7 and win10 pc. Now, this is "normaly" easy fixed,by rejoining the pc to the domain with the domain wizzard in windows. I noticed this didnt work anymore.   I was running without