similar to: Error message dns

Am 31.07.19 um 13:37 schrieb L.P.H. van Belle via samba: > So if i understand correctly. > You removed : /var/lib/samba/private/dns_update_cache > > Stopped samba and started samba and you got the dns A for hostname DC back > in /var/lib/samba/private/dns_update_cache ?? Yes! repeated that once more now. Same result. > Hmm.. >> SOA contains

I am trying to join a Fedora Linux box running Samba 4.1.5 to a Windows Server 2000 domain controller as an additional domain controller. I should mention that our realm is the same as our domain name, adi.com. This is a 15 year old mistake. And the Windows DC does not have all of our machines listed. To work around that I have delegated _msdcs, _sites, _tcp and _udp to the Windows DC with name

Hi, Thank your for your answers. @Rowland: Yes, Winbind is installed but it seems it is not started (or cannot start) @Andrew: Please find extract in log level 4 during a service restart and a connection test with smbclient from another machine. I hope this could help, this is not clear to me : ==> /var/log/samba/log.samba <== [2018/05/29 10:54:00.173894, 0]

Hello! I am on Debian Testing repo. I used this: https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller It works, but every 10 minutes it does this: Feb 9 23:21:13 server samba[875]: /usr/sbin/samba_dnsupdate: ERROR: Record already exists Feb 9 23:21:13 server samba[875]: [2017/02/09 23:21:13.544804, 0]

On Fri, 8 Mar 2019 19:14:32 +0100 Dirk Laurenz via samba <samba at lists.samba.org> wrote: > Hello $LIST, > > > > i setup a new clean domain to examine the feature of > updating/creating PTR records. When i call ipconfig /registerdns on > the client i get this entry in the windows eventlog (sorry german) > > > > Fehler beim Registrieren der

Hello $LIST, i setup a new clean domain to examine the feature of updating/creating PTR records. When i call ipconfig /registerdns on the client i get this entry in the windows eventlog (sorry german) Fehler beim Registrieren der Hostressourceneinträge (A oder AAAA) für den Netzwerkadapter mit den folgenden Einstellungen: Adaptername: {2A467E48-624B-4CCF-9B7D-9BA5629D8117}

On 16/08/2019 14:14, Alexander Harm via samba wrote: > > > > > > 4. apt update &&?apt -t buster-backports install samba attr winbind libpam-winbind libnss-winbind libpam-krb5 krb5-config krb5-user smbclient You are missing the 'acl' package > > 5.?find /var/run/samba /var/lib/samba /var/cache/samba /var/lib/samba/private -name '*.tdb' -name

Ah, OK. Thought that I read this somewhere to first create a DC and then join. So I demote and just try to join straight away? On 16. August 2019 at 15:38:56, Rowland penny via samba (samba at lists.samba.org) wrote: On 16/08/2019 14:14, Alexander Harm via samba wrote: > > > > > > 4. apt update &&?apt -t buster-backports install samba attr winbind

(Ah, just finish my message and Rowland also mosted. Well, see this as extra info ) This "should" not be needed. Run this : https://raw.githubusercontent.com/thctlo/samba4/master/samba-check-SePrivileges.sh bash samba-check-SePrivileges.sh And you see all default settings. And you should see: (everyhere) but i picked SeDiskOperatorPrivilege as example SeDiskOperatorPrivilege:

I joined an existing domain according to: https://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC My var/log.samba shows the following error message ... and unfortunately ... I have no idea what that means. [2013/05/29 20:48:00, 0] ../lib/util/util_runcmd.c:334(samba_runcmd_io_handler) /usr/local/samba/sbin/samba_dnsupdate: tkey query failed: GSSAPI error: Major = Unspecified

Meny thanks for our fast answer ! root at AD:/source# cat /tmp/samba-debug-info.txt Collected config --- 2020-03-23-15:57 ----------- Hostname: AD DNS Domain: Caloro.m FQDN: AD.Caloro.m ipaddress: 192.168.1.7 ----------- Kerberos SRV _kerberos._tcp.Caloro.m record verified ok, sample output: Server: 192.168.1.9 Address: 192.168.1.9#53 _kerberos._tcp.caloro.m service = 0 0 88

Hello Rowland, Thank you very much for your support so far. Now I could join. But: Now I have a problem with the DNS. I use the samba internal DNS. When I try to reach mydom.local or SAD.mydom.local, I only get the error: ? nslookup SAD.mydom.local Server: 192.168.159.98 Address: 192.168.159.98 # 53 Non-authoritative answer: *** Can not find SAD.mydom.local: No answer

Rowland, Just to confirm: after changing the zone to a domain-wide, Samba has successfully performed the join. Samba daemon has also started well, but printed these errors in the log: [2020/02/12 13:03:34.097665, 0] ../../lib/util/util_runcmd.c:352(samba_runcmd_io_handler) /usr/local/samba/sbin/samba_dnsupdate: ; TSIG error with server: tsig verify failure [2020/02/12 13:03:34.169520, 0]

Hello together Installing a new Samba AD on me new installed Debian 10. root at AD:/home/maurizio# /usr/sbin/smbd -V Version 4.9.5-Debian But DNS_Update will by fail: [2020/03/22 13:26:02.266719, 0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) /usr/sbin/samba_dnsupdate: ERROR(runtime): uncaught exception - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') [2020/03/22

Hi, I have two problems with my 2 Samba AD-DC. I don't know if the two problems are related. Both domain controllers show the same error pattern for problem 1.The second problem only occurs with the second domain controller. The domain itself seems to work and be in order. Does someone know where this comes from and how to solve it? ## Issue 1 ## By doing my random log checking, I saw the

2018-12-31 20:50 időpontban L.P.H. van Belle via samba ezt írta: > Can you try to upgrade to any 4.8 version then to 4.9.4? > might work, atleast my guess this will have a better chance get passed > this bug. > I can confirm that an upgrade to 4.7.3 to 4.8.5 works. But! After upgrading the dnsupdate did not work, giving these log messages: [2019/01/02 19:18:42.908955, 0]

On 3/23/2018 8:50 AM, Sven Vogel via samba wrote: > Hi, > > i have the same problem. Inplace upgrade and i get the following > error. > > Mar 23 13:46:50 orion2 systemd[1]: Started Session 30346 of user root. > Mar 23 13:46:50 orion2 systemd-logind[1316]: Removed session 30346. > Mar 23 13:46:50 orion2 sernet-samba-ad[7358]: Shutting down SAMBA AD > services : ..done

On Wed, 2 Jan 2019 19:35:04 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Wed, 02 Jan 2019 20:09:44 +0100 > Král Gergely via samba <samba at lists.samba.org> wrote: > > > 2018-12-31 20:50 időpontban L.P.H. van Belle via samba ezt írta: > > > Can you try to upgrade to any 4.8 version then to 4.9.4? > > > might work, atleast my

On Sat, 8 Jun 2024 17:05:25 +0200 Ronny Preiss via samba <samba at lists.samba.org> wrote: > Hi, > > I have two problems with my 2 Samba AD-DC. I don't know if the two > problems are related. > Both domain controllers show the same error pattern for problem 1.The > second problem only occurs with the second domain controller. > The domain itself seems to work and

This bug affects only upgrade via source or via packages (louis's apt) too? On Wed, Jan 2, 2019 at 8:38 PM Viktor Trojanovic via samba < samba at lists.samba.org> wrote: > > > > On 2 Jan 2019, at 22:43, Rowland Penny via samba <samba at lists.samba.org> > wrote: > > > > On Wed, 2 Jan 2019 19:35:04 +0000 > > Rowland Penny via samba <samba at