similar to: split horizon and authoritative answers..?

Hai, Have you ever tried this with a systemd networking setup. I suggest you try this, this at least helped me with some split dns issues. Below shows how i did it. Configure you network with system, the configs.. #/etc/systemd/network/lan-dev.network # # Configure global settings in /etc/systemd/*.conf # # Dont forget : rm /etc/resolv.conf && ln -s /run/systemd/resolve/resolv.conf

In installed a new DC (Samba 4.12.8 on Ubuntu 20.4) and initially everything appeared to work smoothly. Now I experience issues: DCDIAG /s:cobra.samba.lindenberg.one Directory Server Diagnosis Performing initial setup: [cobra.samba.lindenberg.one] LDAP bind failed with error 1326, The user name or password is incorrect.. With the other DC (still samba 4.11.14 on Ubuntu

I installed a third DC today. Replication works find, but as systemctl status samba-ad-dc showed an error w.r.t. dnsupdate I was running samba_dnsupdate ?verbose. Below is the output. It looks like there are some missing DNS records, but what are potential causes of this error: dns_tkey_gssnegotiate: TKEY is unacceptable I already checked what?s listed @

Ah, ok, my thats where its different here. My setup is AD-DNS => eth0 Server_split_DNS (Proxy) eth1 => internet > -----Oorspronkelijk bericht----- > Van: Joachim Lindenberg [mailto:samba at lindenberg.one] > Verzonden: dinsdag 30 juli 2019 10:44 > Aan: 'L.P.H. van Belle'; samba at lists.samba.org > Onderwerp: AW: [Samba] split horizon and authoritative answers..?

I figured it out myself. The kerberos configuration on the old dc cobra was bad ? no clue why it worked at all until yesterday. After fixing it, testing with kinit, and restarting the dc processes it resumed replication. Joachim Von: Joachim Lindenberg <samba at lindenberg.one> Gesendet: Friday, 19 July 2019 16:54 An: samba at lists.samba.org Betreff: replication stuck? Until

On 22/10/2020 19:49, Joachim Lindenberg wrote: > Password for Administrator at SAMBA.LINDENBERG.ONE: > > Failed to bind to uuid 50abc2a4-574d-40b3-9d66-ee4fd5fba076 for ncacn_ip_tcp:192.168.177.19[49153,sign,target_hostname=cobra.samba.lindenberg.one,abstract_syntax=50abc2a4-574d-40b3-9d66-ee4fd5fba076/0x00000005,localaddress=192.168.177.19] NT_STATUS_LOGON_FAILURE > ERROR: Connecting

Please see replies inline: On 22/10/2020 19:06, Joachim Lindenberg wrote: > root at cobra:/home/joachim# cat /tmp/samba-debug-info.txt > Collected config --- 2020-10-22-17:57 ----------- > > Hostname: cobra > DNS Domain: > FQDN: cobra > ipaddress: 192.168.177.19 I actually expected more output, but lets start with what we have :-) You do not seem to have a domain name, you

On 12/08/2019 20:19, Joachim Lindenberg wrote: > Hi Rowland, > did read, actually cited the page it myself, but didn?t help me to identify the cause. > Kerberos credentials exists, dns users exists, file permission are correct. So either that is insufficient or I am blind.. > Regards, Joachim > > -----Urspr?ngliche Nachricht----- > Von: samba <samba-bounces at

05.12.2023 17:21, Joachim Lindenberg via samba: > I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19, but the Dc is not yet working again. > > systemctl status samba-ad-dc shows: > > Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] ../../source4/samba/service_task.c:36(task_server_terminate) > Dec 05 12:48:39 cobra samba[749]:

I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19, but the Dc is not yet working again. systemctl status samba-ad-dc shows: Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] ../../source4/samba/service_task.c:36(task_server_terminate) Dec 05 12:48:39 cobra samba[749]: task_server_terminate: task_server_terminate: [winbindd child process

Until yesterday replication between my two DCs (boa and cobra) was running fine. Now I am observing one direction boa->cobra being stuck. I noticed this with a missing update of a DNS entry, but samba-tool drs showrepl confirms? Output of cobra shows plenty entries like the following (including just he first of each type): ==== INBOUND NEIGHBORS ====

Sure. Here they are: root at cobra:/var/log/samba# cat /etc/apt/sources.list # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. deb http://de.archive.ubuntu.com/ubuntu focal main restricted # deb-src http://de.archive.ubuntu.com/ubuntu focal main restricted ## Major bug fix updates produced after the final release of the ##

It?s always recommend to demote the DC, upgrade samba, and join the DC again. Did you do it this way ? You may have a broken DC, or a broken installation. Instead of troubleshooting, which you can of course do, I?d demote (or force-demote), reinstall and re join. http://samba.bigbird.es/doku.php?id=samba:upgrade-sama LP On 5 Dec 2023 at 15:45 +0100, Joachim Lindenberg via samba <samba at

I set up a new windows machine and joined it to my existing domain (two Samba DCs). Now it turns out there is a computer in AD, but the associated DNS A/AAAA records of the new machine are missing. I already tried to leave and rejoin, but that didn?t fix the issue. Due to the long ACL I don?t really like the idea of creating the records manually. How can I fix or diagnose that situation?

On 26/10/2020 14:43, Joachim Lindenberg wrote: > > Hi Rowland, > > can I reset the machine password of the DC somehow? > > Thanks, Joachim > yes, see here: https://wiki.samba.org/index.php/Samba_Security_Documentation#Manual_roll-over Also, please do not send posts directly to me, only to the list. Rowland

On 14/11/2020 15:51, Rowland penny via samba wrote: > On 14/11/2020 12:56, Joachim Lindenberg via samba wrote: >> Sure. Here they are: >> >> root at cobra:/var/log/samba# cat /etc/apt/sources.list >> # See http://help.ubuntu.com/community/UpgradeNotes for how to >> upgrade to >> # newer versions of the distribution. >> deb

To fix this, i would start with. First, set the first AD-DC its resolv.conf to SERVER_IP=$(ip -o route get to 8.8.8.8 | sed -n 's/.*src \([0-9.]\+\).*/\1/p') search $(hostname -d) > resolv.conf.new nameserver ${SERVER_IP} >> resolv.conf.new nameserver 8.8.8.8 # because we want a fallback to internet, for now. >> resolv.conf.new mv /etc/resolv.conf{,.backup} mv

From http://samba.bigbird.es/doku.php?id=samba:upgrade-sama 4.20 has a new package samba-ad-dc (split from other binaries in previous versions) that provides DC functionality. Before 4.20, there is a meta-package with the same name that provides compatibility before the upgrade. It is recommended to install this meta package samba-ad-dc before upgrading to 4.20, so the upgrade has all its

On Tue, 5 Dec 2023 15:21:50 +0100 Joachim Lindenberg via samba <samba at lists.samba.org> wrote: > I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> > 4.19, but the Dc is not yet working again. How did you upgrade ? If I remember correctly, both 20.04 and 22.04 come with 4.15.13 (latest Samba version available), so could it be that the upgrade from 20.04 to

On 18/07/2019 16:08, Joachim Lindenberg wrote: > Hi Rowland, > does not match the syntax... > > root at boa:/etc/apt/sources.list.d# unattended-upgrade --dry-run -v > Unable to parse Unattended-Upgrade::Allowed-Origins. > Traceback (most recent call last): > File "/usr/bin/unattended-upgrade", line 2104, in <module> > sys.exit(main(options)) >