search for: bpo12

...in the update notes. > > If I do apt update for example on a member server I get: > /19 packages can be upgraded. Run 'apt list --upgradable' to see > them./ > > apt list --upgradable shows: > /Listing... Done > libldb2/stable-backports 2:2.10.0+samba4.21.3+dfsg-4~bpo12+1 arm64 > [upgradable from: 2:2.10.0+samba4.21.3+dfsg-1~bpo12+1] > libnss-winbind/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64 > [upgradable from: 2:4.21.3+dfsg-1~bpo12+1] > libpam-winbind/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64 > [upgradable from: 2:4.21.3+dfsg-1~bpo12+1...

...pdate. Maybe I simply didn't find it in the update notes. If I do apt update for example on a member server I get: /19 packages can be upgraded. Run 'apt list --upgradable' to see them./ apt list --upgradable shows: /Listing... Done libldb2/stable-backports 2:2.10.0+samba4.21.3+dfsg-4~bpo12+1 arm64 [upgradable from: 2:2.10.0+samba4.21.3+dfsg-1~bpo12+1] libnss-winbind/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64 [upgradable from: 2:4.21.3+dfsg-1~bpo12+1] libpam-winbind/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64 [upgradable from: 2:4.21.3+dfsg-1~bpo12+1] libsmbclient/stable-bac...

...t; If I do apt update for example on a member server I get: > > /19 packages can be upgraded. Run 'apt list --upgradable' to see > > them./ > > > > apt list --upgradable shows: > > /Listing... Done > > libldb2/stable-backports 2:2.10.0+samba4.21.3+dfsg-4~bpo12+1 arm64 > > [upgradable from: 2:2.10.0+samba4.21.3+dfsg-1~bpo12+1] > > libnss-winbind/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64 > > [upgradable from: 2:4.21.3+dfsg-1~bpo12+1] > > libpam-winbind/stable-backports 2:4.21.3+dfsg-4~bpo12+1 arm64 > > [upgradable from...

It seems so, yesterday I got a working update to Samba 4.21.3: ldb-tools 2:2.10.0+samba4.21.3+dfsg-1~bpo12+1 etc. But it seems Michael had it repaired, got just a mail from my apticron service: The following packages are currently pending an upgrade: ldb-tools 2:2.10.0+samba4.21.3+dfsg-5~bpo12+1 libldb2 2:2.10.0+samba4.21.3+dfsg-5~bpo12+1 libnss-winbind 2:4.21.3+dfsg-5~bpo12+1 libpam-winbind 2:4...

...0+deb12u1 is to be installed Breaks: samba-ad-provision (< 2:4.20.5+dfsg) but 2:4.17.12+dfsg-0+deb12u1 is to be installed E: Broken packages The following packages are installed: roy at moggy:~$ sudo dpkg -l | grep samba ii libldb2:amd64 2:2.9.1+samba4.20.5+dfsg-1~bpo12+1 amd64 LDAP-like embedded database - shared library ii python3-ldb 2:2.9.1+samba4.20.5+dfsg-1~bpo12+1 amd64 Python 3 bindings for LDB ii python3-samba 2:4.20.5+dfsg-1~bpo12+1 amd64 Python 3 bindings...

...t's the only reason you've added it). I'm not suggesting to use my repo, just explaining the difference here. Thanks, /mjt > The following packages are installed: > roy at moggy:~$ sudo dpkg -l | grep samba > ii libldb2:amd64 2:2.9.1+samba4.20.5+dfsg-1~bpo12+1 amd64 LDAP-like embedded database - shared library > ii python3-ldb 2:2.9.1+samba4.20.5+dfsg-1~bpo12+1 amd64 Python 3 bindings for LDB > ii python3-samba 2:4.20.5+dfsg-1~bpo12+1 amd64 Python 3...

On Tue, 6 Aug 2024 20:41:51 +0200 Anders ?stling via samba <samba at lists.samba.org> wrote: > Hello > I have an older Debian 11 with Samba 4.13 as domain member serving som > industrial systems with files. > Today I decided to upgrade both Debian (to 12) and Samba (to 4.17 and > then 4.20). The upgrade using the backport repo worked after some > extra steps. Som

...en I'm do: --------------------- root at dc01:~# smbclient -L cluster Password for [EXAMPLE\root]: Anonymous login successful Sharename Type Comment --------- ---- ------- IPC$ IPC IPC Service (Samba 4.21.2-Debian-4.21.2+dfsg-3~bpo12+1) admin-share Disk admin share auf dem Cluster daten1 Disk Mit glusterfs_fuse SMB1 disabled -- no workgroup available ------------------- I'm getting the result with anonymous access. That's ok. Then I do: ------------------ root at dc01:~# kinit ad...

...; root at dc01:~# smbclient -L cluster > Password for [EXAMPLE\root]: > Anonymous login successful > > Sharename Type Comment > --------- ---- ------- > IPC$ IPC IPC Service (Samba > 4.21.2-Debian-4.21.2+dfsg-3~bpo12+1) > admin-share Disk admin share auf dem Cluster > daten1 Disk Mit glusterfs_fuse > SMB1 disabled -- no workgroup available > ------------------- > I'm getting the result with anonymous access. That's ok. Then I do: > -------------...

...samba/rpcd_lsad --configfile=/etc/samba/smb.conf --worker-group=3 --worker-index=5 --debuglevel=0 Oct 04 13:05:45 SERVER-2 winbindd[5679]: [2024/10/04 13:05:45.154727, 0] source3/winbindd/winbindd.c:1450(main) Oct 04 13:05:45 SERVER-2 winbindd[5679]: winbindd version 4.20.5-Debian-4.20.5+dfsg-1~bpo12+1 started. Oct 04 13:05:45 SERVER-2 winbindd[5679]: Copyright Andrew Tridgell and the Samba Team 1992-2024 Oct 04 13:05:45 SERVER-2 systemd[1]: Started winbind.service - Samba Winbind Daemon. Oct 04 13:05:45 SERVER-2 samba-dcerpcd[5685]: [2024/10/04 13:05:45.228787, 0] source3/rpc_server/rpc_hos...

On Fri, 4 Oct 2024 10:11:37 +0200 Emmanuel Florac <eflorac at intellique.com> wrote: > Le Thu, 3 Oct 2024 21:35:04 +0100 > Rowland Penny via samba <samba at lists.samba.org> ?crivait: > > > > Yes, I mean Windows 11 or WIndows Server 2022 machines that are > > > registered into the AD. A Win11 PC which isn't AD-connected (but > > > in the same

...what Linux distro you are using and how you > > set up the RODC and fileserver, what is in their smb.conf files for > > instance ? > > All samba servers are debian12 samba on domain members is > 4.17.12-Debian while on RODC is backports version > 4.21.1-Debian-4.21.1+dfsg-2~bpo12+1 It might be worth considering upgrading the domain members. > > The smb.conf of RODC was generate at join time: > > # Global parameters > [global] > dns forwarder = 8.8.8.8 8.8.4.4 > netbios name = LVSRVDC > realm = INTRA.COMUNE.TRENTO.IT > server role = active...

...You also haven't told us what Linux distro you are using and how you > set up the RODC and fileserver, what is in their smb.conf files for > instance ? All samba servers are debian12 samba on domain members is 4.17.12-Debian while on RODC is backports version 4.21.1-Debian-4.21.1+dfsg-2~bpo12+1 The smb.conf of RODC was generate at join time: # Global parameters [global] dns forwarder = 8.8.8.8 8.8.4.4 netbios name = LVSRVDC realm = INTRA.COMUNE.TRENTO.IT server role = active directory domain controller workgroup = INTRA [sysvol] path = /var/lib/samba/sysvol read only = No [ne...

...cannot exclude that in the past few months the connection between RODC and RWDC's dropped for some brief period due to our testing. >> All samba servers are debian12 samba on domain members is >> 4.17.12-Debian while on RODC is backports version >> 4.21.1-Debian-4.21.1+dfsg-2~bpo12+1 > > It might be worth considering upgrading the domain members. Ok, i upgraded one of the 3 domain members to backports version 4.21.1-Debian-4.21.1+dfsg-2~bpo12+1 >> >> The smb.conf of RODC was generate at join time: >> >> # Global parameters >> [global] &g...

On Tue, 3 Dec 2024 09:15:36 +0100 Mitja Tav?ar via samba <samba at lists.samba.org> wrote: > Hi, i have some problems with a recently joined Read Only Domain > controller. > > I had 2 Domain Controllers based on Windows Server 2019 (hosts > vmw2srvdc1 an vmw2srvdc2). I and i recently added a new site (PSN) > and Read Only DC in this second site based on samba (host

...e okay to change, including having significant changes in packaging and upstream version changes too. Debian backports always "tracks" testing, - I mean, each package in backports is a backport from testing in a hope it will be useful. Samba is not an exception here, - I upload stuff to bpo12 once something intersting happens with samba in trixie. An interesting part here is that *packaging* changes happens *not* when switching to a new upstream version (be it samba or not) - unless upstream changes too much so significant packaging changes are needed too. On the contrary, most packag...

Here are the lines of the winbind.log justs after a restart of winbind: [2024/09/25 07:32:24.878544,? 1] ../../source3/winbindd/wb_lookupsid.c:102(wb_lookupsid_recv) ? Failed with STATUS_SOME_UNMAPPED. [2024/09/25 07:32:41.921563,? 0] ../../source3/winbindd/winbindd_dual.c:1964(winbindd_sig_term_handler) ? Got sig[15] terminate (is_parent=1) [2024/09/25 07:32:42.042654,? 0]

Hello mjt, I can only speak for myself: For bigger upgrades (e. g. samba 4.19 -> 4.20) Im manually updating a few servers and check if everything works. For smaller updates (e. g. 4.20.1 -> 4.20.2) Im using saltstack to automate updating the servers. It suppresses these messages and this is fine in 99% of all cases because a minor update is not supposed to change much (e. g. split a