similar to: [Announce] Samba 4.20.7 Available for Download

Release Announcements --------------------- This is the latest stable release of the Samba 4.21 release series. Changes since 4.21.3 -------------------- o? Vinit Agnihotri <vagnihot at redhat.com> ?? * BUG 15780: Increasing slowness of sharesec performance with high number of ???? registry shares. o? Jeremy Allison <jra at samba.org> ?? * BUG 15782: winbindd shows memleak in

Release Announcements --------------------- This is the latest stable release of the Samba 4.21 release series. Changes since 4.21.3 -------------------- o? Vinit Agnihotri <vagnihot at redhat.com> ?? * BUG 15780: Increasing slowness of sharesec performance with high number of ???? registry shares. o? Jeremy Allison <jra at samba.org> ?? * BUG 15782: winbindd shows memleak in

Release Announcements --------------------- This is the latest stable release of the Samba 4.21 release series. Changes since 4.21.2 -------------------- o? Douglas Bagnall <douglas.bagnall at catalyst.net.nz> ?? * BUG 15701: More possible replication loops against Azure AD. o? Ralph Boehme <slow at samba.org> ?? * BUG 15697: Compound rename from Mac clients can fail with ????

Release Announcements --------------------- This is the latest stable release of the Samba 4.21 release series. Changes since 4.21.2 -------------------- o? Douglas Bagnall <douglas.bagnall at catalyst.net.nz> ?? * BUG 15701: More possible replication loops against Azure AD. o? Ralph Boehme <slow at samba.org> ?? * BUG 15697: Compound rename from Mac clients can fail with ????

I'm using the Yocto Project to build an embedded distro, to which I'm adding Samba 3.6 from OpenEmbedded. Doing so increases my root file system from about 63MB to 175MB. I seem to be building a large Samba server with a small ancillary operating system tacked onto it. I listed the files in my file system image, and see that lots of the commands are quite large. I understand that Samba 4

Dear all, Following [1] from a year ago, I'd like to know what is the state of the crossrename VFS module, and whether it's expected to be supported at least together with the recycle module? To be honest I'm quite sympathetic with the reasoning in [1] and I don't see a general use of crossrename. However, it remains relevant in the context of recycle, and currently I

Hi all, I am running slackware 8.0, 2.4.20 with GCC 2.95.3. Old but it works J I am trying to compile Samba 3.6.3 but get the following: Compiling lib/sharesec.c lib/sharesec.c: In function `delete_share_security': lib/sharesec.c:382: incompatible types in return The following command failed: gcc -I../lib/zlib -O -I. -I/home/steve/samba-3.6.3/source3

Hi, I tried samba 4.12.0 on our file server which is a domain member and exporting some shares. We're getting some strange errors on some shares since the update. Right after starting or restarting smbd everything is fine. After short while (seconds or a few minutes) users are getting errors when trying to access the shares, e.q. "Invalid Handle Error", "An unexpected

On 10/03/2020 08:03, Andreas Hauffe via samba wrote: > We have a kerberized NFS4 running on that machine, too. I do hope that you are not resharing the NFS share(s) via Samba, that way lies madness ;-) Try this smb.conf: [global] ??????? workgroup = SUBDOM ??????? realm = SUBDOM.DOM.EXAMPLE.COM ??????? security = ADS ??????? bind interfaces only = Yes ??????? interfaces = lo enp1s0f0

Thanks, I will give that a try. But I need the 'winbind separator = +'. We use some expensive commercial software (e.g. ANSYS, ABAQUS, ...), which uses shell scripts to start their software under linux. These scripts are not able to handle a backslash in the user name. The only solution was to switch to a "+" character. We reported these issues two years ago. Regards,

Hi all, Is this something I should report in bugzilla? In my smb3.conf I have vfs object = recycle full_audit crossrename and when doing a classicupgrade, I'm getting a segmentation fault. It doesn't finish. (tried 4.1.2, 4.1.3, 4.1.4) When removing the line, the classicupgrade finishes successfully. It's easy to get around, but wouldn't it be nicer not to crash..?

On 31/01/2023 06:59, Peter Milesson via samba wrote: > Hi folks, > > The smb.conf and other information after specification of the problems. > > The journal on a AD domain member server is cluttered with permission > denied entries of this message pair: > > ?? Jan 31 07:02:26 konsrvfast smbd[436004]: [2023/01/31 > ?? 07:02:26.083500,? 0, effective(11025, 10515),

Hi folks, The smb.conf and other information after specification of the problems. The journal on a AD domain member server is cluttered with permission denied entries of this message pair: Jan 31 07:02:26 konsrvfast smbd[436004]: [2023/01/31 07:02:26.083500,? 0, effective(11025, 10515), real(11025, 0)] ../../source3/smbd/smb2_service.c:168(chdir_current_service) Jan 31

Hi, we have a stange problem here since samba 4.12. Users on specific clients are not allowed to access a share after reboot of the client and in very rare cases suddenly during use. When we restart the smb service after the access denied message on the client for a share, the user is allowed to access the share. So there seems no problem with permissions. Are there any known reasons for

Release Announcements --------------------- This is the latest stable release of the Samba 4.15 release series. Changes since 4.15.3 -------------------- o? Jeremy Allison <jra at samba.org> ?? * BUG 14928: Duplicate SMB file_ids leading to Windows client cache ???? poisoning. ?? * BUG 14939: smbclient -L doesn't set "client max protocol" to NT1 before ???? calling the

Release Announcements --------------------- This is the latest stable release of the Samba 4.15 release series. Changes since 4.15.3 -------------------- o? Jeremy Allison <jra at samba.org> ?? * BUG 14928: Duplicate SMB file_ids leading to Windows client cache ???? poisoning. ?? * BUG 14939: smbclient -L doesn't set "client max protocol" to NT1 before ???? calling the

Hello everyone, I'm preparing a migration from a NT4-mode domain controller 3.5 to version 4.19. The migration process is going well, but from the share management MMC, no matter the share defined in the smb.conf, when I try to access the authorization tab, I get the following message in the Samba logs: Apr 25 11:39:58 svdom01.voillot205 rpcd_classic[1827]: [2024/04/25 11:39:58.511922, 0]

On Thu, 25 Apr 2024 11:44:42 +0000 Philippe Maladjian via samba <samba at lists.samba.org> wrote: > Hello everyone, > > I'm preparing a migration from a NT4-mode domain controller 3.5 to > version 4.19. The migration process is going well, but from the share > management MMC, no matter the share defined in the smb.conf, when I > try to access the authorization tab, I

Hi Michael, On Thu, Aug 18, 2016 at 11:42:12AM +0200, Michael Adam wrote: > From reading the original post, I get the impression > that the problem is associated to the share root directory. nope. It will happen with just any directory or file created from a non SMB client, eg mkdir|touch (or NFS, ...) on the server. It is also associated with files or directories created from Windows

On Thu, 25 Apr 2024 11:44:42 +0000 Philippe Maladjian via samba <samba at lists.samba.org> wrote: > Hello everyone, > > I'm preparing a migration from a NT4-mode domain controller 3.5 to > version 4.19. The migration process is going well, but from the share > management MMC, no matter the share defined in the smb.conf, when I > try to access the authorization tab, I