similar to: problem this morning - need help

Hello. I've got a network of FreeBSD servers which traditionally hosted a classic domain. I upgraded some months ago, removing the old PDC and BDC and migrating to an AD DC controller in a jail. This is working fine with Samba 4.4.13. Now I'm trying to add a second DC, so I created a new jail on another physical server and went on with the setup, following: >

[2023/03/28 11:32:15.524325, 0] ../../lib/util/util_runcmd.c:352(samba_runcmd_io_handler) /usr/sbin/samba_dnsupdate: ERROR: Record already exist; record could not be added. zone[starmans.lan] name[nobel] [2023/03/28 11:32:15.542955, 0] ../../lib/util/util_runcmd.c:352(samba_runcmd_io_handler) /usr/sbin/samba_dnsupdate: ERROR: Record already exist; record could not be added.

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]

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

I would have assumed that deleting all the NTDS connections for all the DCs would have remedied this issue. I'll write a patch to try to avoid this error in any case. Ignoring this error and answering your earlier question, it's often hard to tell if the KCC is doing what is expected or not. To figure that out, you need a lot more information about the network topology configuration,

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

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

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

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 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

Hi folks, The last log record from journalctl -xeu winbind directly after winbind startup is: Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate failed with exit status 1 For completeness, the log entries for winbind startup is displayed below. Things seem to work though, but I have never seen it before (I don't like error messages). When I noticed the message I

Dear All, I have a setup with samba acting as active directory domain controller, DNS updates are done via bind DLZ. I have recompiled it to allow spnego. DHCP server is external, no changes in it are possible. Domain members try to register in the DNS, KDC is aware of them, however no DNS entries for them are created and BIND returns errors. Any hints are welcome since I really need it working.

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

On 9/18/2016 6:23 PM, Garming Sam wrote: > Hi, > > For the unsorted attributeID values errors, can you first try: > > samba-tool dbcheck --cross-ncs --fix --yes 'fix_replmetadata_unsorted_attid' > > There's too much going on, and it does look like it might be bailing > out. Running it with 'fix_replmetadata_unsorted_attid' should fix those > first

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

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 Mar 23 13:46:50 orion2 systemd[1]: Stopped LSB: initscript for the SAMBA AD services. Mar 23

On Thu, 13 Jun 2024 16:26:17 +0200 Peter Milesson via samba <samba at lists.samba.org> wrote: > Hi folks, > > The last log record from journalctl -xeu winbind directly after > winbind startup is: > > Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate > failed with exit status 1 > > For completeness, the log entries for winbind startup is

On 13.06.2024 20:33, Peter Milesson via samba wrote: > > > On 13.06.2024 17:21, Rowland Penny via samba wrote: >> On Thu, 13 Jun 2024 16:26:17 +0200 >> Peter Milesson via samba <samba at lists.samba.org> wrote: >> >>> Hi folks, >>> >>> The last log record from journalctl -xeu winbind directly after >>> winbind startup is:

On 13.06.2024 17:21, Rowland Penny via samba wrote: > On Thu, 13 Jun 2024 16:26:17 +0200 > Peter Milesson via samba <samba at lists.samba.org> wrote: > >> Hi folks, >> >> The last log record from journalctl -xeu winbind directly after >> winbind startup is: >> >> Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate >>