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

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

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 (

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

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

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

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 11/01/2019 09:19, Administrator TOOTAI wrote: > Le 11/01/2019 à 10:12, Neil Youngman a écrit : >> A while back, I posted about detecting when a call was picked up by a >> fax machine. It was suggested that having a "fax" extension and >> "faxdetect=yes" would cause it to jump to the "fax" extension. This >> was not something I could

Hallo, I've just updated my slackware samba packet from 3.6.17 to 4.1.6. My start script is not changed, it still calls "nmbd -D" and "smbd -D". Seems to run as expected. But now I get strange messages like [2014/04/15 10:36:05.535423, 0] ../source3/lib/ util_sock.c:423(open_socket_in) open_socket_in(): socket() call failed: Die Adressfamilie wird von der

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/

In my environment the selftest for samba3.rpc.spoolss.printer was failing at source3/script/tests/printing/modprinter.pl(138) with the Perl error in subject: Insecure $ENV{ENV} while running setgid at /home/user/src/samba-git/samba/source3/script/tests/printing/modprinter.pl line 138 code is: ============================== delete @ENV{'BASH_ENV'}; $ENV{'PATH'} =

 Hi, list,     I recently begin to study samba source code. Now I have some questions to ask. Can you give me some help?     The first question is what the relationship between samba versions(such as 3.x.x , 4.x.x) and samba3/samba4. In samba source code, I find two directories, souce3 and soure4. Do they mean  samba3 and samba4?  Actually, almost all docs in samba are about samba3, where to find

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

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

Hi folks, I have an issue at a weird confluence of macOS Mojave's "nsmb" client, Adobe Lightroom and Photoshop, and Samba 4.7.6-Ubuntu. Since I don't have much control over Apple or Adobe software, I'm hoping there's some smb.conf magic (or other sage advice) that might help me out of this jam. For reference, Samba is configured for SMB2-only access (i.e. durable file

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

On 7/25/19 3:28 PM, Leroy Tennison wrote: > If you don't want multiple DNS server entries on the client I'm ok with them, only the problem is that the clients take their timeouts when a server is unreachable, and users panic. > then a master and (possibly multiple) slave server configuration can be set up (I'm assuming ISC DNS - their solution to redundancy/failover is master

Attached is a patch which adds a log= directive to authorized_keys. The text in the log="text" directive is appended to the log line, so you can easily tell which key is matched. For instance the line: log="hello world!",no-agent-forwarding,command="/bin/true",no-pty, no-user-rc,no-X11-forwarding,permitopen="127.0.0.1:7" ssh-rsa AAAAB3Nza....xcgaK9xXoU=

Hi all, I've got on AD DC using Samba 4.4.3 on Centos7 which accept Kerberos connections (kinit is working), which accept ldapsearch with credentials but which refuse ldapsearch with GSSAPI. The issue does not seem to be coming from the client as I discovered this issue writing a script to test all 22 DC, and all 21 others DC are working well from that client. The error: SASL/GSSAPI

On 7/25/19 7:58 PM, Paul Heinlein wrote: > On Thu, 25 Jul 2019, hw wrote: > >> On 7/25/19 3:28 PM, Leroy Tennison wrote: >>> If you don't want multiple DNS server entries on the client >> >> I'm ok with them, only the problem is that the clients take their >> timeouts >> when a server is unreachable, and users panic. > > On Linux