similar to: Samba broken after dist-upgrade in Ubuntu 20.04?

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

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

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

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

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

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 http://de.archive.ubuntu.com/ubuntu focal main restricted > # deb-src http://de.archive.ubuntu.com/ubuntu focal main

Hai, ? Debian Buster Samba 4.13 is now online on my repo. Info : https://apt.van-belle.nl/ With the release of 4.13 the following changes are going to happen in the repo's. Current (recently sended?list) OS-sambaXXXX with EOL wont be supported anymore, upgrade your OS and/or Samba versions! EOL repo's will stay online for about 6 months, that gives sufficient time to upgrade.

hai, ? To explain this a bit more. All my repo's are set per os and samba version. So as long you dont change the sambaXXX version, you stay on that version and minimze risk with changes in samba. Its always :? http://apt.van-belle.nl/debian? And all you change is :??? buster-samba412? Current available versions are : stretch-samba410 stretch-samba411 buster-samba411 buster-samba412

>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 >22.04 managed to install unrequired packages ? I did a do-release-upgrade first to go from 20.04 to 22.04, and then updated my /etc/apt/sources.list.d/mjt.list to go from focal/samba-4.18 to jammy/samba-4.19. I also

Hello, I trying to install samba 4.11 from the repository http://apt.van-belle.nl/ and have an error. Err:4 http://apt.van-belle.nl/ubuntu bionic-samba411 Release regards.

Hey Andre,? Sure, we already on the latest Patch Level on Ubuntu with 2:4.13.17~dfsg-0ubuntu1.20.04.4 Installer, but the issue still exist.? The only way to resolve the issue and to make a login possible again, was the workaround in my previous mail.? The Windows clients are Windows 10 22H2 with all updates installed. We also doesn't have any special settings in smb.conf. If you have any

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

Hai, ? Sorry for the Delay, bit overloaded with work, but the end is near. pff, finaly.. soon i take a long vacation.. ? Well, you know the drill.. Ubuntu 20.04 focal, is next. ? For the Raspbian guys, please try how the buster-samba412 works for you and let me know the results. Rapsbian will be last to build so if you in a need for the newer versions, use/try ?buster-samba412? !! and dont

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 @

We have the same issue with Samba 4.13.17. For Ubuntu 20.04 with Samba 4.13.17 there seems to be only a workaround to solve the login problem: Modifying the Local Security Policy -> Local Policies -> Security Options -> Network security: "Configure encryption types allowed for Kerberos" Check only DES_CBC_CRC, DES_CBC_MD5 and RC4_HMAC_MD5. ? This worked for us to login again. ?

> On 21/08/2020 07:18 Plutocrat <plutocrat at gmail.com> wrote: > > > On 21/08/2020 02.53, spamvoll at googlemail.com wrote: > > is anyone using the "Bionic (18.04 LTS)" packages on? Focal?Fossa?(20.04 LTS) ? > > I'm not sure if its working after the upgrade > > Not quite sure what you're saying here, but if you ran the "sudo

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

Hi all, I am testing R 4.0 and ran into an issue with timezones on Ubuntu Focal: converting a timestamp to another timezone results in NA: as.POSIXct(as.POSIXlt(Sys.time(), tz = "CET"), tz = "EST") This only happens on Ubuntu Focal, it seems to work fine on Ubuntu Bionic. I am the standard ubuntu docker image icw/ r-base from Dirk's ppa:edd/r-4.0 on both systems. Am I