Displaying 20 results from an estimated 10000 matches similar to: "Upgrade Samba with latest backports packages"
2025 Jan 12
1
Upgrade Samba with latest backports packages
On Sun, 12 Jan 2025 14:02:59 +0100
Ingo Asche via samba <samba at lists.samba.org> wrote:
> Hi Michael,
>
> there seems to be a trick necessary to upgrade Samba with the latest
> backports update. 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
2025 Jan 12
1
Upgrade Samba with latest backports packages
On Sun, 12 Jan 2025 13:41:54 +0000
Rowland Penny via samba <samba at lists.samba.org> wrote:
> On Sun, 12 Jan 2025 14:02:59 +0100
> Ingo Asche via samba <samba at lists.samba.org> wrote:
>
> > Hi Michael,
> >
> > there seems to be a trick necessary to upgrade Samba with the
> > latest backports update. Maybe I simply didn't find it in the
>
2025 Jan 12
1
Upgrade Samba with latest backports packages
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
2024 Nov 06
2
Upgrading from samba version 4.20.5 to 4.21.1 using Debian Bookworm-backports
Hi
I tried to update a member server's samba version from 4.20.5 to 4.21.1 using Bookworm-backports and get the following error:
roy at moggy:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if
2024 Nov 06
2
Upgrading from samba version 4.20.5 to 4.21.1 using Debian Bookworm-backports
06.11.2024 12:50, spindles seven via samba wrote:
> Hi
> I tried to update a member server's samba version from 4.20.5 to 4.21.1 using Bookworm-backports and get the following error:
>
> roy at moggy:~$ sudo apt upgrade
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Calculating upgrade... Done
> Some packages
2025 Feb 10
1
Problems after DC upgrade
Well, it almost went okay.
Thumbnail: I had two DCs, running the latest in buster. I created a new one running bookworm and 4.21.3. I joined the new machine as a DC. I then transferred the FSMO roles from one of the old ones and demoted that one. My plan is to create a fourth new one and demote the other old one. But, two problems:
1. The dns on the new DC is not responding. It did
2024 Dec 20
1
smbclient and Kerberos authentication
Hi to all,
I''m just writing the next version of the german Samba-book and I'm just
testing smbclient so when I'm do:
---------------------
root at dc01:~# smbclient -L cluster
Password for [EXAMPLE\root]:
Anonymous login successful
Sharename Type Comment
--------- ---- -------
IPC$ IPC IPC Service (Samba
2020 Jun 19
1
Upgrading from Debian Stretch to Buster, Van Belle package
Am 19.12.19 um 19:15 schrieb Lmloge via samba:
> When upgrading use : apt-get dist-upgrade --autoremove
> Which is needed to replace and remove optional samba packages.
> In the step from 4.10 to 4.11 the upgrade might stop.
> Then use: apt --fix-broken install
> That should remove libldb1 and upgrade contineus with installing libldb2.
hijacking this older thread now:
Did an
2018 Mar 19
3
Fwd: Re: Erro Upgrade Samba 4.6.3 to 4.8
Hi!
Thanks for answer.
Start-Date: 2018-03-19 12:00:50
Commandline: apt-get install winbind
Install: python-crypto:amd64 (2.6.1-4ubuntu0.2, automatic),
update-inetd:amd64 (4.43, automatic), python-samba:amd64
(4.3.11+dfsg-0ubuntu0.14.04.14, automatic), winbind:amd64
(4.3.11+dfsg-0ubuntu0.14.04.14), tdb-tools:amd64
(1.3.8-0ubuntu0.14.04.1, automatic), samba:amd64
2025 Feb 10
1
Problems after DC upgrade
On Mon, 10 Feb 2025 02:24:31 +0000
Stephen Brandli via samba <samba at lists.samba.org> wrote:
> Well, it almost went okay.
>
> Thumbnail: I had two DCs, running the latest in buster. I created a
> new one running bookworm and 4.21.3. I joined the new machine as a
> DC. I then transferred the FSMO roles from one of the old ones and
> demoted that one. My plan is to
2015 Aug 19
1
upgrade-ing samba on debian jessie. ( 4.1.17 to 4.2.3 sernet ) fails and solutions.
hai,
?
Just an informational message and below the fixed for the problems..?
?
when upgrading a member server with debian jessie with samba 4.1.17? with samba and winbind installed.?
?
For me this was on?my print server.
?
steps to take.
?
setup the apt sources for sernet.
?
install the sernet packages.
apt-get install sernet-samba sernet-samba-winbind sernet-samba-common sernet-samba-libs
2025 Feb 10
3
Problems after DC upgrade
It was systemd-resolved. I disabled that. Now samba is binding to the port.
But I'm still getting the dnsupdate failure.
And, I can't ping anything. I get the "unknown host or service" error. So names are not getting resolved on the machine. I have to admit to complete ignorance about how this part of linux works. When running systemd-networkd, what normally does name
2023 Feb 15
2
Van Belle Packages & Samba 4.15
Previously, I needed to downgrade Louis samba packages to Buster's
defaults, which would then be upgraded to 4.13 by the dist-upgrade to
Bullseye. This was on a Domain Member, so didn't touch my DC's or have to
worry about DB format stepping (I hope).
apt install samba=2:4.9.5+dfsg-5+deb10u3 python-samba
samba-common=2:4.9.5+dfsg-5+deb10u3 samba-common-bin=2:4.9.5+dfsg-5+deb10u3
2025 Feb 10
1
Problems after DC upgrade
You need to remove the symlink /etc/resolv.conf (probably points to
/run/systemd/resolved/stub-resolv.conf) and create a new /etc/resolv.conf
that has your DC as nameserver.
Den m?n 10 feb. 2025 15:57Stephen Brandli via samba <samba at lists.samba.org>
skrev:
> It was systemd-resolved. I disabled that. Now samba is binding to the
> port.
>
> But I'm still getting the
2024 Aug 06
3
Upgrade from 4.13 to 4.20 failed
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
2019 Dec 20
4
Upgrading from Debian Stretch to Buster, Van Belle package
Ok,
Run :
apt install samba winbind acl
Dont worry if it errors out.
I m out for a quick run for some food, im back in about 30 min.
Louis
> -----Oorspronkelijk bericht-----
> Van: Lmloge [mailto:lmloge at orange.fr]
> Verzonden: vrijdag 20 december 2019 12:11
> Aan: L.P.H. van Belle
> CC: samba at lists.samba.org
> Onderwerp: Re: [Samba] Upgrading from Debian Stretch
2019 Dec 20
4
Upgrading from Debian Stretch to Buster, Van Belle package
Ah, ok,
apt-get remove libldb1 ldb-tools
Then try again : apt install samba winbind acl
The replacement of libldb1 to libldb2 is missing something.
I'll have a look at that.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: Lmloge [mailto:lmloge at orange.fr]
> Verzonden: vrijdag 20 december 2019 13:15
> Aan: L.P.H. van Belle
> CC: samba at lists.samba.org
2016 Apr 19
3
Samba4 quit working after update
Here's what I get at level 0 right after stopping/starting Samba:
[2016/04/19 12:27:06.043469, 0]
../source4/smbd/server.c:372(binary_smbd_main)
samba version 4.3.8-Ubuntu started.
Copyright Andrew Tridgell and the Samba Team 1992-2015
[2016/04/19 12:27:06.157629, 0]
../source4/smbd/server.c:490(binary_smbd_main)
samba: using 'standard' process model
samba: setproctitle not
2020 Jun 19
2
Upgrading from Debian Stretch to Buster, Van Belle package
looks like you have apt pinning enables.my repo is set to 500
default is 990.?
check /etc/apt/ and it's contents
Greetz,
Louis
Op 19 jun. 2020 17:54 schreef "Stefan G. Weichinger via samba" <samba at lists.samba.org>:
Am 19.06.20 um 17:11 schrieb Stefan G. Weichinger via samba:
> Am 19.12.19 um 19:15 schrieb Lmloge via samba:
>
>> When upgrading use :
2016 Apr 19
2
Samba4 quit working after update
There is no winbindd--it was never installed. I don't recall exactly why I
didn't install it, but I seem to recall something about Samba4 in an AD
domain control role not needing it. I ended up using SSS instead.
Sanatized smb.conf:
# Global parameters
[global]
workgroup = DCS
realm = DCS.LOCAL
netbios name = SERVER
server role = active directory domain