similar to: Subject=Re: Mac Clients Disconnect with: source3/smbd/service.c:1050(close_cnum) closed connection to service data

I notice the Configure Samba to Work Better with Mac OS X has been radically shortened?not sure why, but you may want to look at my original 22 Apr 2019 version in the history. You may want to put vfs objects in Global. Note in the vfs_fruit man page: Be careful when mixing shares with and without vfs_fruit. OS X clients negotiate SMB2 AAPL protocol extensions on the first tcon, so mixing shares

Yes, I've tried all of them at this point. I spent some time focusing on SMB2 due to various sources indicating they target it for stability (example: Configure Samba to Work Better with Mac OS X [ https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X] ). Thanks for the suggestion though. I've now been trying out the various Apple specific flags in vfs_fruit (

Hello, I have an issue where Macs running a wide range of OS versions all drop connections at seemingly random intervals, but usually after some long period of time less than 24 hours. The Windows clients keep their connections, however. I can test this in PowerShell with a loop like the following: PS C:\Users\louis> while($true) { Add-Content Z:\_smbcheck\windwows-client.txt $DT; Start-Sleep

Hi Rowland, Thanks for the advice. I've tried your suggestions, but the problem persists. It's strange that it only happens with Macs. I know this is a Samba list, but have encountered anything like this pertaining to Macs in the past? Many thanks, Louis

Louis - have you run testparm -s on your server? You don?t show it in your smb.conf, but I assume you have vfs objects = catia fruit streams_xattr there as well as in your [data] share. If you don?t, you should since you have various fruit: parameters in the [global]. The SMB conversation in your Wireshark pcap would be easier to read if you filter on ?smb2? :-) Todd

On your Samba server, check build options: #: smbd -b - look for vfs_catia, vfs_fruit, vfs_streams_xattr modules. If you have the vfs_ modules, then take a look at this: https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X <https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X>

On 29/10/2019 13:59, L.P.H. van Belle via samba wrote: > Hai, > > Personaly, i agree with Todd, having a few clear examples with the samba versionnumbering in it. > > How about, adding a sub page in : > https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X > > With something like a section that shows : "User contributed examples" > >

Am 22.11.19 um 16:28 schrieb Matthias Leopold via samba: > > > Am 22.11.19 um 15:12 schrieb torch via samba: >> On your Samba server, check build options: #: smbd -b - look for >> vfs_catia, vfs_fruit, vfs_streams_xattr modules. >> >> If you have the vfs_ modules, then take a look at this: >> >>

When I created the User Documentation page "Configure Samba to Work Better with Mac OS X?, my intent was to help others in the same situation I am: I have a WD MyCloud (Gen1) running an old version of samba (4.3.11) with no expectation that the firmware would be upgraded for the latest & greatest samba. The device is still usable, but was not optimized for Macs, so I ssh?d into the

Hai Daniel, Yes yes.. As you can see in my change log. ( found here, http://downloads.van-belle.nl/samba4/Buildlogs/stretch-experimental/ ) >From my changelog. samba (2:4.9.0+dfsg-1.1nmu~deb9) stretch; urgency=medium . * Non-maintainer upload. * Rebuild from Debian stretch from Debian Experimental * Bump build-depends cmocka 1.1.2 * enabled --enable-spotlight to make TimeMachine work

Dear Todd, Thanks for all of the suggestions, yes testparm comes back fine. It used to complain but, Rowlands original suggestion silenced the complaints, except for one: rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) But that's been around for years before the issue at hand. Wilfred Smith's Wireshark suggestion on Stack Exchange eventually took the focus away

And sorry, to answer your question here's what the smb.conf's looked like: SERVERA - Ubuntu 18.04 (Samba 4.7.6) sudden issue: Hi Louis, > When you get a chance, it seems like a number of our excel files were > corrupted. We can't seem to open them at all. I tried opening them from R > and SPSS. > They give different errors: > My error (mac): > Excel cannot open the

Hello I am trying to integrate OS X 10.10.4 clients into existing Samba infractructure run by our IT department. We are currently using Samba 4.2.3. File share is stored on iSCSI array with ext4 filesystem which should support both ACL and XATTR. We are trying to setup vfs_fruit module to avoid possible performance problems on OS X clients. We do NOT user netatalk. Current vfs_fruit config:

Is it possible to backup Mac OS devices through a Samba share on Samba 4.4.6 on Fedora 24 with Time Machine? I am able to successfully advertise the share through Avahi, connect to it in Finder, and read/write files. I am also able to see the share as a destination in Time Machine, but selecting it shows an error that "The selected network backup disk does not support the required

Hi All, at work all our clients are macs (10.10 yosemite). We are trying to move from the classical afp file server to a samba based file server. After a lot of testing, things now works more or less: a mac server acts as Kerberos+OpenLDAP and a linux debian 7 box is doing the file server with samba 4.2.0. A client which has "joined" (which is bound in mac jargon) the

Listing directories with many files (10000+) from a Windows client is nociceably slower when vfs_fruit is enabled on the samba server compared to the same setup without vfs_fruit. On my setup it's roughly 2.5 times slower. To me it looks like this is caused by the getxattr call which is only present with vfs_fruit activated and introduces an additional delay of ~ 0.00033 s per listed

I have a share with approximately 5000 folders in the base directory. The performance on an OS X client is somewhat less than exciting. I compiled the latest Samba 4.3 tarball and enabled fruit per the modules man page, however directory listing performance still takes a few seconds. I've cranked the fruit debug level up to 10 and can see that it is getting used ("fruit_stat called for

> On 11/02/2019, at 10:02 AM, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Mon, 11 Feb 2019 09:14:03 +1300 > Russell Fulton via samba <samba at lists.samba.org> wrote: > >> I am an old UNIX and Mac hand but new to samba. My ultimate aim is >> to use a samba share with Time Machine. I have built an up to date >> version of samba

Hello, I have a unix server (arch linux) with samba 4.1.14. The share has files inside which where created directly on the server. Linux and OSX (10.10.1) clients should access the share and store files. When I mount this samba share into the osx client (10.10.1), files created directly on the server with special names like `File with "quotes"` are displayed mangled (`C7XSWH~V`) on the

On Wed, Dec 12, 2018 at 04:37:43PM +0100, Ralph Böhme via samba wrote: >On Wed, Dec 12, 2018 at 03:35:00PM +0100, Stephan Roth via samba wrote: >>My goal with activating vfs_fruit was to speed up directory listings >>for Mac clients, which works. Can the accompanying slowdown for >>Windows clients be avoided? > >yeah, I guess so, but somebody has to dig through the