similar to: Copy a directory from macOS to Samba fails

On Wed, Oct 05, 2016 at 05:00:52PM +0200, Leander Schäfer via samba wrote: > When copying to QNAP NAS Samba server instead, all works fine - No need for > "xattr -d com.apple.FinderInfo filename" on macOS side before copying. > There must be a smb.conf solution to this?! man vfs_fruit Cheerio! -slow

When copying to QNAP NAS Samba server instead, all works fine - No need for "xattr -d com.apple.FinderInfo filename" on macOS side before copying. There must be a smb.conf solution to this?! Thanks Am 05.10.16 um 15:28 schrieb Leander Schäfer via samba: > Hi, > > unfortunately copying a directory from macOS to a Samba share fails, > if the macOS set ACLs in the source

Hi. I'm testing samba 4.2.0 vfs_fruit on Fedora Server 22-alpha. I confirmed that ResourceFork and FinderInfo are compatible with Netatalk 3.1.7. However, EAs are incompatible. The character ":" in EA name is wrong. The EAs are not seen from clients. smb.conf: [test2] path = /export/test2 writable = yes vfs objects = catia fruit streams_xattr fruit:locking =

Hi, Thank you for your feedback, Andrew. Since Samba is not the only application making use of the TLS_CIPHER_SUITE negotiation rules in ldap.conf, I would like to ensure that all of them still use the highest encryption possible. Currently I had to remove "TLS_CIPHER_SUITE" as a workarrou d in order to let Samba work wirh LDAP in TLS mode. Does anyone have a suggestion how I can apply

On Sun, Dec 27, 2015 at 02:33:10AM +0900, HAT wrote: > Sat, 26 Dec 2015 17:22:56 +0000, Rowland penny <rpenny at samba.org>: > > On 26/12/15 17:08, HAT wrote: > >> Hi, > >> I'm testing samba 4.3.3 vfs_fruit on Fedora rawhide. > >> > >> The EAs are not seen from clients yet. > >> > >> smb.conf: > >> path =

Hi HAT! Nice to meet you over here... ;) On Wed, Mar 11, 2015 at 11:30:45PM +0900, HAT wrote: > Hi. > I'm testing samba 4.2.0 vfs_fruit on Fedora Server 22-alpha. > I confirmed that ResourceFork and FinderInfo are compatible with > Netatalk 3.1.7. However, EAs are incompatible. > The character ":" in EA name is wrong. > The EAs are not seen from clients. >

On Fri, Dec 18, 2015 at 01:14:25AM +0900, HAT wrote: > Hi, > > >> not sure, but the colon in xattr names is probably not handled > >> correctly at this point. Can you please file a bugreport so we can > >> track this? > > > > Bug 11162 > > https://bugzilla.samba.org/show_bug.cgi?id=11162 > > I tested samba 4.3.1 on Fedora 23 and rawhide.

Hi, I make use of shadow_copy2 and root preexec. The vfs root preexec is responsible to auto create home directories which initially don't exist. The script behind it is well tested and works perfectly. Unfortunaltely shadow_copy2 seems to be called before root preexec and fails due to the missing ZFS home share which causes the session to fail completely before root preexec even has a

What would be a working TLS_CIPHER_SUITE in ldap.conf for Samba 4. I'm asking, cause I had to remove TLS_CIPHER_SUITE TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!MD5:!3DES:@STRENGTH from my ldap.conf for samba to work. This wasn't documented anywhere. I think this should be mentoined in the wiki as well as in the man smb.conf under tls.

On 26/12/15 17:08, HAT wrote: > Hi, > I'm testing samba 4.3.3 vfs_fruit on Fedora rawhide. > > The EAs are not seen from clients yet. > > smb.conf: > path = /export/test1/ > writable = yes > vfs objects = catia fruit streams_xattr > fruit:locking = netatalk > fruit:encoding = native > streams_xattr:prefix = user.

Hi Rowland, do you maybe have any idea what could potentially cause this bug? smbclient thrwos me back a mount error(5): Input/output error when I try to mount the remote smbFS. It doesn't happen with my MacOSx and Windows 7 as client but it happens with Linux OSs and with a Konica Minolta copy machine with a scanner to samba function. The first try to mount fails with the above error.

Hello, Using samba 4.11.6+dfsg-0ubuntu1.5 (shipped with Ubuntu 20.04) I'm having trouble with a macOS (10.15.7) client moving files to a share. The server is using zfs for storage, but I can replicate with ext4 too. I spun up a test container with the following minimal config: [global] log level = 7 workgroup = WORKGROUP server string = %h server (Samba, Ubuntu) log file =

Hi, I have been able to successfully install Samba4 and OpenLDAP and connect them via SSL. The file samba.schema is also loaded into OpenLDAP, but when I start samba server it looks like it is expecting some basic structure. My Question at this point is how to provide this the easisest way? Currently the OpenLDAP DB is entirely empty (virgin) so Samba4 could create anything it needs. cat

> not sure, but the colon in xattr names is probably not handled > correctly at this point. Can you please file a bugreport so we can > track this? Bug 11162 https://bugzilla.samba.org/show_bug.cgi?id=11162 -- HAT

Hi sorry to bother, but all of a sudden after a fresh install of samba with the regular smb4.conf it keeps on failing when users try to authenticate: smbclient -U MyUser \\\\MyServerName\\MyShare MyPassword session setup failed: NT_STATUS_UNSUCCESSFUL [...] check_ntlm_password: authentication for user [MyUser] -> [MyUser] -> [MyUser] succeeded [2014/05/02 10:29:40.930648, 3]

In case of FreeBSD, the name of the extended attribute is wrong. % lsextattr user ICONandEA.txt ICONandEA.txt netatalk.Metadata com.apple.TextEncoding com.apple.metadata:kMDItemFinderComment "netatalk.Metadata" is incompatible to Netatalk. The first atom "org." is removed. source3/include/smb.h: /* Prefix for DosStreams in the vfs_streams_xattr module */ #define

Hi list, we have migrated a single node Samba server from Ubuntu Trusty to a 3-node CTDB Cluster on Debian Bullseye with Sernet packages. Storage is CephFS. We are running Samba in Standalone Mode with LDAP Backend. Samba Version: sernet-samba 99:4.18.2-2debian11 I don't know if it is relevant here's how we have mounted CephFS on the samba nodes: (fstab):/samba /srv/samba ceph

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello James, have you ever tested the pv-drivers on W2k SP4? ;-) At first there is a little failure in install.bat. The version-number of w2k starts with "5.00" instead of "5.0.". So your script couldn''t recognize w2k. The rest of the installation looks ok, but after rebooting the vm nothing happens. Theres still the

On 02/05/16 15:08, Stefan Schäfer wrote: > Hi Mathias, > > greping in the output of "net cache list" shows: > > Key: IDMAP/GID2SID/20513 Timeout: Mon May 9 07:29:11 > 2016 Value: S-1-5-21-1891182457-2156988848-2018633412-513 > Key: IDMAP/GID2SID/100 Timeout: Mon May 9 07:29:32 2016 Value: > S-1-5-21-1891182457-2156988848-2018633412-513 >

Am 18.03.2017 um 10:43 schrieb Rowland Penny via samba: > On Sat, 18 Mar 2017 07:48:27 +0100 > Stefan Schäfer via samba <samba at lists.samba.org> wrote: > >> Hi List, >> >> I found some threads here in the list with similar problems, but >> nothing helped to solve my problem. >> >> We have a very much to old Samba DC (Version 4.1.x) and a new