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

(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 ( https://www.samba.org/samba/docs/current/man-html/vfs_fruit.8.html), though with no success thus far. Example settings tried in smb.conf: [global]

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

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

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>

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: >> >>

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: > > https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X

I'm testing the AIX binaries for 3.0.24 and have run into a problem. Depending on how I map the share (using: \\[IP, hostname or FQDN]\[sharename]) then the connection to the server is closed after just a few seconds of inactivity. The server runs on AIX5.3 with the latest fixpack. The client is Win XP SP2. I'm currently using 3.0.22 on our production server and don't have this

Hello again I have one more followup question. it looks to me like the server is restarting here just after it closes the shares: [2009/03/12 09:13:34, 1, pid=7541] /SourceCache/samba/samba-187.8/ samba/source/smbd/service.c:close_cnum(1284) hwi-eas149 (172.26.15.62) closed connection to service encodedrive8 [2009/03/12 09:13:34, 1, pid=7539] /SourceCache/samba/samba-187.8/

Greetings I am running SMB on OS X Server 10.5.6, it's not clear what version of SMB they use. I have a Windows XP box that mounts a network drive on the server. This mount disappears from time to time for no apparent reason: [2009/03/12 08:35:54, 2, pid=23189] /SourceCache/samba/samba-187.8/ samba/source/smbd/process.c:timeout_processing(1371) Closing idle connection [2009/03/12

After upgrading to macOS 10.15 I've hit an issue where if the share's connection is interrupted for long enough (e.g. because the server is rebooted) then the client Mac's Finder becomes stuck and?puts up a message 'The operation can?t be completed because the original item for ?<share>? can?t be found. Sometimes restarting Finder helps, sometimes restarting sharingd helps

Hi I apt installed Samba Version 4.9.5-Debian (latest in their repos) on a fresh-built Raspbian Buster Lite release 2020-02-05. I put together the configuration outlined below by using the docs at https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X and https://www.samba.org/samba/docs/current/man-html/vfs_fruit.8.html. The underlying usb hard drive is an ext4 partition

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" Rowland *(and Ralph), what do you guys think? Why not add a section like that for most things.

> Please keep the wiki page simple. Anyone who wants to get > down and dirty > has to read man vfs_fruit and understand what the options are > really for > and he probably also has to understand the code. Its not about getting down and dirty, but about gettings a simple setup for samba version X.YY for users that are more beginners. And exactly my point a beginner, will fail,

I'm trying to compile R on AIX 6.1. gcc -v Using built-in specs. Target: powerpc-ibm-aix6.1.0.0 Configured with: ../gcc-4.4.5/configure --with-as=/usr/bin/as --with-ld=/usr/bin/ld --enable-languages=c,c++,fortran --prefix=/opt/freeware --enable-threads --enable-version-specific-runtime-libs --disable-nls --enable-decimal-float=dpd --host=powerpc-ibm-aix6.1.0.0 Thread model: aix gcc version

I'm trying to compile R on AIX 6.1. gcc -v Using built-in specs. Target: powerpc-ibm-aix6.1.0.0 Configured with: ../gcc-4.4.5/configure --with-as=/usr/bin/as --with-ld=/usr/bin/ld --enable-languages=c,c++,fortran --prefix=/opt/freeware --enable-threads --enable-version-specific-runtime-libs --disable-nls --enable-decimal-float=dpd --host=powerpc-ibm-aix6.1.0.0 Thread model: aix gcc version

Why do you want TM to work over samba? Not sure it is supported completely by Apple although they did have developer documentation on it at one time: https://developer.apple.com/library/archive/releasenotes/NetworkingInternetWeb/Time_Machine_SMB_Spec/ I did see this on reddit, but have not tried it personally: