similar to: replication stuck?

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

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

Am 22.07.19 um 10:39 schrieb Stefan G. Weichinger via samba: > Am 20.07.19 um 11:54 schrieb Joachim Lindenberg via samba: >> 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. > > pls show how you

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

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 @

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

I need to implement split horizon DNS, as I have just one external IP address (dynamic.lindenberg.one in external DNS) but multiple internal ones. External requests are distributed by port or using sniproxy (in particular 443), and all externally visible names are in a distinct zone then my domain, but with an additional indirection: names like backup.lindenberg.one resolve to CNAME

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

?? And we did compair this months ago.. You did say, everything is in sync now. Ahhh... ;-) If you really want to know if you DC's are setup the same. Tip.. Copy /etc of both server into a new folder. And runn diff -r /etc-dc1/ /etc-dc2/ > check-me.txt And check-me.txt I just did that on my brand new Buster proxy servers, 2 with keepalived. I'm almost done with this, you

"--seize" helped: root at pre01svdeb03:~# samba-tool fsmo show SchemaMasterRole owner: CN=NTDS Settings,CN=PRE01SVDEB03,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=pilsbacher,DC=at InfrastructureMasterRole owner: CN=NTDS Settings,CN=PRE01SVDEB03,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=pilsbacher,DC=at RidAllocationMasterRole owner:

Am 31.07.19 um 15:59 schrieb L.P.H. van Belle via samba: > Ok, after that reboot > > ! Note, atm dont care about secrets.keytab (yet) > .. I was a bit ahead with things... > > One thing at a time, for the keytab to be corrected, you need a perfect correct working > A PTR CNAME GUIDs for the DC(3) first then we start thinking in kerberos corrections. > > Run

Am 31.07.19 um 17:54 schrieb Stefan G. Weichinger via samba: > Am 31.07.19 um 17:33 schrieb L.P.H. van Belle via samba: > >> Which is the DC with FSMO roles, if its DC1 then move them to pre01svdeb03.pilsbacher.at >> Remove/purge this DC and join clean again. ( no need to reinstall os etc. just samba ) > > What? > > uninstall samba? > or unjoin from domain

Hai, And thanks for the other check i needed to know if the A record did exist. >> ldap1 CNAME pre01svdeb02 >> ldap2 CNAME pre01svdeb03 >sorry, typo -------------^ Yes i was expecting that. ;-) What i see, all SOA record and serialnr are same where is should be so thats ok. What i noticed is this part. dig a dc.pilsbacher.at @192.168.16.205/206 replies. DNS1 ( DC1

I forgot. dig a pre01svdeb02.pilsbacher.at @192.168.16.205 dig a pre01svdeb02.pilsbacher.at @192.168.16.206 Can you run these also for me. And there are no CNAMEs pointing to the AD-DCs ?

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

Good morning Stefan. Your welkom. I see everything worked out now. Great !! Well done, you made it happen. :-) What i suggest now, at least these are the steps i always do to make sure the DC's are having a exact same setup. First, i clear all my logs and reboot one server. Wait 15-30 min, then go through all you logs, fix every warning/error. Make it perfect. Reboot again, repeat

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

On 31/07/2019 12:04, Stefan G. Weichinger via samba wrote: > Am 31.07.19 um 12:50 schrieb Rowland penny via samba: >> On 31/07/2019 11:40, Stefan G. Weichinger via samba wrote: >>> Am 31.07.19 um 12:32 schrieb Rowland penny via samba: >>>> On 31/07/2019 11:22, Stefan G. Weichinger via samba wrote: >>>>> "dc" was the old name a few years ago

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

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