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

(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]

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

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

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 (

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

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

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

Hello, Sorry to bother all with this simple configuration question, Little background: I recently migrated our samba server from Ubuntu 9.04 to Ubuntu 14.04.1.LTS. Migration was done like this: moving conf-files from the old server to the new one. My samba server is member of a windows domain, that is controlled by a Domain Controller running Windows Server 2008. We have three types of shares,

Hello, Sorry to bother all with this simple(?) configuration question, Little background: I recently migrated our samba server from Ubuntu 9.04 to Ubuntu 14.04.1.LTS. Migration was done like this: moving conf-files from the old server to the new one. My samba server is member of a windows domain, that is controlled by a Domain Controller running Windows Server 2008. We have three types of

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/

Dear everybody, Could anybody told me the reason? Does the code of samba 3 and samba 4 mix together in the master branch. How can I let smbd be compiled from source4/smbd/server.c? Thanks and Have a good weekend Jun The following is what I got from the command line: junyij-2.desktop$ ./smbd [2012/09/28 17:36:18, 0] ../lib/util/debug.c:592(reopen_logs_internal) Unable to open new log file

I've updated samba from Samba version 3.0.24 ( config file in testparm-oldsrv1.txt) to Samba version 3.0.33-3.29.el5_5.1 ( config file in testparm-newsrv1b.txt) I've used samba to share a directory which is used to windows 2000 serve as mapped drive. All works fine with samba 3.0.24, but i've a problem in new version: Every 10 minutes the client (w2k server) is disconnected from

I'm using FC8 Server with Samba 3.0.30-fc8 and have an erratic problem assecing the share. I have a Share that every one can acess and I use the nobody user to acess everithing without any problem, and from time to time when user tries to acess a file the share gets closed, than we have to resart the machine and it goes wel again. the log for one user is below why does it closes the

Hello, I'm looking for an explanation of the errors we are seeing in syslog pertaining to samba. This is an AIX 5.2 ML04 samba server running version 3.0.7 of samba. The ones we see the most are the following: 1.) Jan 4 04:16:40 server smbd[104176]: getpeername failed. Error was A socket must be already connected. 2.) Jan 4 04:16:40 server smbd[104176]: write_socket_data: write

Hello everybody, I have a strange failure in my samba environment ( samba 2.2.3a ), when users try to open files on a samba share via the windows explorer. I see the following messages in the samba log file : hcnch049 (10.12.48.103) connect to service homedir as user pa015276 (uid=8065, gid=8048) (pid 19565) [2002/08/01 08:54:09, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb

Hello everybody, I have a strange failure in my samba environment ( samba 2.2.3a ), when users try to open files on a samba share via the windows explorer. I see the following messages in the samba log file : hcnch049 (10.12.48.103) connect to service homedir as user pa015276 (uid=8065, gid=8048) (pid 19565) [2002/08/01 08:54:09, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb

Issue: Three WinXP Pro boxes using Offline Files disconnect from all Samba shares when a user either performs a synch or accesses a file on the share with offline files enabled. About half the time, being able to reconnect for any length of time requires a reboot of the WinXP machines. Disabling the Offline Files in Windows alleviates the problem. Background and Network

Hi, I noticed that smbcontrol smbd reload-config or service smbd reload doesn't reload include files. Is there anyway to get a reload to reload files that have been included from the main smb.conf ? Otherwise it only looks like restart works, but that causes connections to reset, even in a ctdb/clustered environment . The only other option it looks like is to just put everything into the