samba - Jul 2022 - Issue related to the backup being made on the server

On Thu, 2022-07-07 at 09:27 +0200, Nitin Nair via samba
wrote:
> Hello,
>  
> We have an application and we were trying to create backup onto the
> network drive(\\fileserver3\nitinnair ) but its throws an error
> saying  "Backup failed ...make sure to have writable folder for all
> users" even though I have access to it as you can see from the
> screenshot mentioned.Can you let me know why I am facing this issue?
> Before creating a backup onto a server wasn't a problem. 
Sorry, no screenshot, was it an attachment ? This list strips
attachments.

What OS ?

What version of Samba ?

Has anything been updated ?

Please post the output of 'testparm -s' when run on the Samba server.

Rowland

Hi Rowland,

I am working with Nitin on this problem, he is programming our windows software,
I am server administrator.
>> We have an application and we were trying to create backup onto the
>> network drive(\\fileserver3\nitinnair ) but its throws an error
>> saying  "Backup failed ...make sure to have writable folder for
all
>> users" even though I have access to it as you can see from the
>> screenshot mentioned.Can you let me know why I am facing this issue?
>> Before creating a backup onto a server wasn't a problem. 
> What OS ?
server side is "Red Hat Enterprise Linux release 8.6 (Ootpa)"
client side is Windows 10 21H1
> What version of Samba ?
smbd version 4.15.5 
> Has anything been updated ?
both server and clients are kept up to date.
server side:
2022-02-16T07:56:36+0100 SUBDEBUG Upgraded: samba-4.14.5-7.el8_5.x86_64
2022-03-16T14:49:34+0100 SUBDEBUG Upgraded: samba-4.14.5-9.el8_5.x86_64
2022-05-17T10:50:29+0200 SUBDEBUG Upgraded: samba-4.14.5-10.el8_5.x86_64
2022-07-05T12:24:21+0200 SUBDEBUG Upgraded: samba-4.15.5-5.el8.x86_64

The problem may have appeared between April and June.
> Please post the output of 'testparm -s' when run on the Samba
server.
--8<---
# testparm -s
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowed

Server role: ROLE_STANDALONE

# Global parameters
[global]
        domain master = Yes
        log file = /var/log/samba/log.%m.%R
        max log size = 10000
        os level = 200
        preferred master = Yes
        printcap name = cups
        read raw = No
        security = USER
        server min protocol = SMB3
        wins support = Yes
        workgroup = PAMAS
        write raw = No
        idmap config * : backend = tdb
        acl allow execute always = Yes
        cups options = raw


[homes]
        browseable = No
        comment = Home Directories
        create mask = 0700
        directory mask = 0700
        read only = No
        valid users = %S


[common]
        comment = allgemein zugaengliche Daten
        create mask = 0770
        directory mask = 0770
        force directory mode = 0020
        force group = common
        path = /mnt/raid/samba/common
        read only = No
        valid users = @common

the problem appears on the home-share as well as on the common share. There are
other shares that have been removed from the output.



I hope that helps...




-- 
Mit freundlichen Gr??en,
Michael Schumacher