similar to: new dc does not allow login..?

Hi Rowland, sorry - I am always unsure whether it makes sense to send intermediate discussion to the full list, especially when it is likely to result in more questions than answers - imho this is noise not relevant to all. I?d be happy to summarize the solution afterwards if deemed interesting to others. I downloaded sources to get to the scripts and located them, but usage is not really clear to

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

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

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 @

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?

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

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

Hello, I installed updates today on my Ubuntu 20.04 and after that, Samba was disabled/masked/not installed at all. Even attempting to install samba again reports: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of

You copied the certificate file?? Am 22. Juli 2019 12:46:34 MESZ schrieb Joachim Lindenberg <samba at lindenberg.one>: >Hi Stefan, >> pls show how you fixed it >See >https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory#Kerberos >for the test. My fix was to take the one generated on the newer DC also >to the older one. >Joachim --

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

Hi Joachim, > Op 15 feb 2024 om 23:09 heeft Joachim Lindenberg via samba <samba at lists.samba.org> het volgende geschreven: > > ?Hi Rowland, > No, I don?t have so many devices yet. Rowland believes that one should not use IPv6 internally. Many disagree. > But I know some organizations that want to switch to IPv6 consistently and you can rephrase my question to whether

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

Hi Tim, then I believe there is a bug. I did not specify the option and it used /etc/smb.conf rather than the correct /etc/samba/smb.conf. I was running a local backup on DC with Louis build 4.10.6 on ubuntu 18.04.2. Shall I open a ticket? Best Regards, Joachim -----Urspr?ngliche Nachricht----- Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Tim Beale via samba Gesendet:

Hi Rowland, i.e. we probably have to help Jeremy finding a setup that makes this reproducible. Seriously this implies it can be a difference in users, authorizations, linux, samba, or windows installation or configuration. I was testing with a user that is a domain administrator. I just tested with a non-admin-user, also crashes. My samba is 4.10.6 from Louis running on Ubuntu 18.04.2 running

Ok, with the smb.conf change and then samba_dnsupdate --rpc-server-ip=192.168.177.19 --use-samba-tool --verbose I got no error messages. Shall I now revert the change? Monitor? At present samba_dnsupdate has nothing to do.. Thanks, Joachim -----Urspr?ngliche Nachricht----- Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Rowland penny via samba Gesendet: Monday, 12 August

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

Its fixed now. I'll add an extra test so this wont happen again. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > L.P.H. van Belle via samba > Verzonden: maandag 16 november 2020 8:57 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Samba broken after dist-upgrade in > Ubuntu 20.04? >