How to ensure newly created files on network drive are read-write for everyone? ------------------------------------------------------------------------ **In brief.** When a user creates a document/file on the network server volume at /users/shared/"M C"/, the document ends up being editable only for the user who created it and Read-Only for everyone else. I need it be editable for everyone. **Specifics** With the client user Mac account 'AAA', a file is created on the networked drive in a folder called 'M C' in /users/shared. **The permissions for that newly created file will be Read-Write only for user 'AAA' and undesirably Read Only for the 2 other users listed: 'Staff' and 'Everyone'. I want it to be 'Read-Write' for everyone** (or preferably for only certain users but I'll settle for everyone right now) Similarly, if a Mac user 'BBB', in the same way as 'AAA', connects to the server and creates a file, it will be Read-Write for 'BBB' but Read-Only for all other users. I need all newly created and edited files to be editable by all users. The files in that directory need be shared. **Environment** The client Mac runs macOS 13 (Ventura). The server runs macOS 12 (Monterey) but may upgrade it soon to macOS 15 (Sequoia). User 'AAA' connects to server using their own (sharing only) Mac account on that server. The folder 'M C' is shared: The folder 'M C' has been added to the list at System Settings > Sharing > File Sharing > Shared Folders. Its 'Get Info' window has 'Shared' ticked. The folder 'M C' has Read-Write permissions listed for the users 'AAA', 'BBB', 'Staff', and 'Everyone'. This is shown in both 'Get Info' window and sharing control panel. **What I've tried already** I applied Read-Write permissions to the folder 'M C' for all users but that doesn't help. The contents are unaffected (as expected). I applied Read-Write permissions to the folder 'M C' for all users and all contents but that doesn't help. Existing files will get Read-Write permissions for all users but thereafter, newly created files will be Read-Write only for 'AAA'. Where possible, I tried making these changes in both the Finder's 'Get Info' window, and the System Settings > Sharing control panel. In the System Settings > Sharing control panel, in desperation, for the folder 'M C', I even secondary-clicked it > Advanced Options > ticked 'Allow guest users', but that did not help. (Other options there are not ticked) I have tried placing the folder in other locations (eg, server's home folder), but it makes no difference and I figure /users/shared/ ought be the safest option for this to work. Can anyone help with this issue?

As of macOS Big Sur or Catalina, folders shared via File Sharing have a banner when viewed in Finder: Is there any way to hide this banner without removing the folder from File Sharing?

When I mount a remote SMB volume with macOS's file sharing feature like as: osascript -e 'mount volume "smb://USER@MACOS_SERVER/VOLNAME" but it fails with Error -5014. What I tried were: - rebooting the client - restarting smbd with kill/launchctl on the server - on/off "File Sharing" at "Sharing" of Preferences app. Any ideas?

I am trying to find out why my MacBook Pro will not connect to my QNAP NAS. When attempting to use Finder in macOS to access the files on the NAS, it tries to connect but fails each time. When attempting to click "Connect As..." at the top right of the Finder window, it simply attempts to connect again without prompting you for a username and password as it typically would in the past. Things that I can confirm: - All other computers on my network (Windows and Linux) are able to access the NAS - The MacBook has been able to connect to the NAS successfully in the past with no problems, however, I don't recall how far back it stopped working - I can ping the NAS IP Address from the MacBook - I have ensured that the NAS settings have Apple file sharing protocols enabled - The NAS does appear in the Finder window's sidebar, you just cannot access it. Equipment: - MacBook Pro (Mid 2015) running macOS Catalina 10.15.4. - QNAP TS-251 NAS w/ most recent updates.

I have this weird issue on Sonoma where after creating a sharing-only user I'm unable to select it under Windows File Sharing. Instead I only see an entry for my main account (+ other Standard/Admin accounts), which is sometimes duplicated: Creating a second sharing-only account just results in yet another duplicate of my main, and so on: This occurred both before and after a full factory reset (OS + data).

I have some Ubuntu Servers running Samba with Winbind. Everything is fine, but Macs will randomly disconnect overnight, or at some irregular interval. On the servers, Samba logs this as two events: 1: ../source3/smbd/service.c:1050(close_cnum) 2: closed connection to service data By matching timestamps on the Macs I can see they log the drops as: kcm DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?; set a breakpoint on _dispatch_bug_deprecated to debug By analyzing timestamps I have determined that this is the only event logged on the Mac clients' side. Here is an example client that has a shell script writing to a text file on a share every ten seconds: You can see the connection was alive at 08:59:46 in the text file on the left, and in /var/log/system.log there's only a single relevant message. I asked on the Samba list serve about it and have been told the Macs are simply closing the connections. ---------- #Update: Wireshark analysis shows some additional information: Errors from above (Line 4): - STATUS_NETWORK_SESSION_EXPIRED - SATATUS_INVALID_PARAMETER - STATUS_NETWORK_NAME_DELETED Here is the final SMB2 message (second from bottom): Negotiate Protocol Response: As if to confound, there's an NT Status: STATUS_SUCCESS messages in there (see annotation). Here is what Microsoft says about the error: > If the Status field in the SMB2 header is > STATUS_NETWORK_SESSION_EXPIRED, the client MUST attempt to > reauthenticate the session that is identified by the SessionId in the > SMB2 header, as specified in section 3.2.4.2.3. If the > reauthentication attempt succeeds, the client MUST retry the request > that failed with STATUS_NETWORK_SESSION_EXPIRED. **If the > reauthentication attempt fails, the client MUST fail the operation and > terminate the session**, as specified in section 3.2.4.23. Is there a script I can run to just renew the session in a cron job? End update ---------- ---------- Other types clients will keep the connections open forever, so it does indeed seem like only Macs are doing this. The OS versions vary from OS X 10.12 to macOS Catalina, using various flavors of SMB2 to SMB3. Any idea how I can begin to understand why the macs are doing this, or any tips on getting them to keep the connections alive? The Mac clients are running jobs that rely on a persistent connection. ---------- **Highly relevant to know, but originally left out as I was looking for a workaround:** I have about a dozen of these servers (mostly Ubuntu 18.04; Samba 4.7.6) running fine for the past several years. Three of them had automatic updates installed, and these three have the issue of the Macs disconnecting. I'm holding back letting the other servers restart for the updates, and the Macs will not drop connections to the non-updated servers. As a test I setup a server to 16.04 to see if and older version of Ubuntu Server would pose the same issue. Surprisingly it has the same problem using a different version of Samba (4.3.11). I will have to do the test again, without letting 16.04 install the latest security updates, in order to confirm my suspicions that those are the cause of the problem. Though I suspect something in Ubuntu's core changed, I am asking here since only Macs are affected. ---------- On a number of Macs with OSes from 10.12 to Catalina I have tried testing them with their default settings, and all possible combinations of changes to /etc/nsmb.conf: [default] signing_required=no protocol_vers_map=[see manpage for nsmb.conf (linked below)] manpage for nsmb.conf I've also tried disabling all sleep and powersaving options, and even using a nice cafffinate wrapper, KeepingYouAwake , to enforce this. On the server I've tried following the advice of another sysadmin on the #macosx freenode channel , kode54, who shared how they eventually got a stable connection . The advice didn't help–well I haven't fully tried it as it requires installing a version of Samba from a PPA for a version of Samba maintained by the Linux for Schools Project –but informed me of vfs_fruit and the fact that there is a developmental effort of extending Samba through an extra package for, in part, dealing with Macs . It also led me to find a page on Samba's wiki discussing difficulties with Macs and server-side workarounds: *Configure Samba to Work Better with Mac OS X * It's difficult for me to try installing suggested Samba PPA because these servers are fileservers in part only, and are generally always being used for compute jobs that can take days to run (neuroimaging processing). They were built for compute jobs, and do storage almost as a side-effect of the dual-socket, high-memory density, server options also happening to be the servers with the large number of drive bays (16+). I'm hoping to try other options before becoming fully negatively disruptive. Since none of the server-side options are helping–I've been trying the flags in various combinations no to avail–I am hoping that the Apple community will have some workaround for me. Any way of keeping a persistent connection, despite where the issue may originate, would be incredibly valuable.

I've got a mac (OS X 10.8.2) that's accessing files on an Win7 SMB share. About half the time the Mac comes back from suspend it can't connect to the SMB share. The Win7 machine is on and the password hasn't changed. But when I try to connect to the SMB server it asks for the username/password. When I type it in, I get told it's wrong. Then I restart the machine (Mac) and it can connect to the SMB server fine. It's an annoyance really, especially when I've got 8 different terminal windows open and they're all named the way I like etc. Anyone got a suggestion/tips for re-connecting to an SMB drive after suspend?

I used to be able to access folders on my remote systems without problem. Now in Catalina when I find my computers on my LAN and try to connect to them, I can only see the contents of ~/ and that of any folder I made. The default folders (such as Documents, Downloads appear empty, something I've confirmed my navigating to it in the terminal. I *assume* this is another idiotic protect-the-user-from-themself-at-all-cost-even-if-it-messes-with-normal-users move in Catalina, but how can I actually access the folder? I'm logged in as myself, so there should be no permissions issue (all other folders/files have the same permissions anyways). On the remote end, by screensharing at the exact same time I can confirm that there are files present in the folders. No dialog is presented asking for access like many apps do now to access such files. I even added my home folder as a separate shared folder, and granted full access to everyone. But to no avail. Any ideas on how to enable access?

I want to know if there is any way to log events for every file upload, download, creation, modification (including create, edit, delete), and transfer/sharing on macOS — regardless of whether these events occur in browsers or other applications. My goal is to identify which file was uploaded or downloaded, and if possible, determine the destination or source URL for network transfers, despite encryption (HTTPS). I understand that getting a full-proof solution might not be feasible using a single method, and I'm open to combining several approaches. I prefer not to use a proxy-based solution because: - A proxy can interfere with existing services if one is already running on the host. - Proxies can add inefficiency and performance overhead. - I do not need to block events; I only want to monitor and log them. I have considered these options: 1. **Audit Logs / OpenBSM:** Using the macOS audit framework to log file system events (file creations, modifications, deletions) is one possibility. This can capture low-level file operations, but it does not directly correlate file operations with network upload or download events. 2. **Endpoint Security Framework (ESF):** ESF can observe system events such as file accesses and process activities. While it can efficiently log file events, an inherent challenge is to correlate these system-level events with network-level events (i.e. to determine which file has been uploaded, and *where* — the URL or hostname). 3. **Dynamic Instrumentation / Hooking:** Hooking network system calls (or even HTTPS library functions such as SSL_write) using tools like Frida could capture plaintext data before encryption. However, this raises challenges: - Handling different network libraries (SecureTransport vs. OpenSSL). - Ensuring reliability in capturing HTTP/HTTPS uploads. - Accurately correlating intercepted network data with file system activity. **Primary Challenges:** - **Correlating Files with Network Uploads:** I need to not only log when a file operation occurs locally but also determine the corresponding network event (for instance, an HTTP POST request to an upload URL) that transfers the file. - **Handling Encrypted Traffic:** Most modern browsers use HTTPS by default. Intercepting such traffic to extract payload details (like file names) involves overcoming challenges in TLS decryption, which is non-trivial without proxying or in-depth instrumentation. **My Question:** Is there a unified or combined approach to monitor and correlate file system events (uploads/downloads, modifications) with the network requests that represent those file transfers on modern macOS (e.g., macOS Sequoia 15.4.1)? In essence, how do I: - Log detailed file events (creation, modification, deletion) using the built-in macOS tools like the Audit Framework or Endpoint Security Framework? - Correlate these file events with network activity (uploads/downloads) to determine which file was transferred to which website? - Handle HTTPS-encrypted traffic to reliably extract the transfer details (e.g., target URL/hostname), without resorting to a proxy solution? I would appreciate any insights, sample code, or references on how to achieve this using macOS-native mechanisms, dynamic instrumentation, or a combination of both approaches. Thanks in advance for your help!

Running Big Sur 11.5 and trying to use File Sharing to access my drive on my local network. I only wish to allow the primary user access so I set the permissions accordingly ("everyone" has no access). However, after ~1 day (hard to figure out exactly when), the permissions will revert, allowing anyone read access which is the default setting. This occurs without rebooting, the only operations being connecting to the SMB share and waiting some amount of time. Is there something I'm doing wrong with the configuration? I've looked into alternative network file sharing servers (even just brew install samba) but can't find anything with good documentation besides the native SMB file sharing.

I have a smb folder on my Mac mini. That is perfectly reachable from my MacBook Finder app but not from my iPad Pro Files app. I am completely puzzled. I use the same user/password from both devices trying to reach the same location. All three devices are in the same (WLAN) network. Calling for help to debug or a solution.

My desktop Mac mini (2018) shares files to other computers on the network. I've set it up in System Preferences > Sharing so that only known users can connect, with their username and password. If I go to restart my Mini, I sometimes get a message to say that 1 or more users are connected. **Is there an easy way to find out which users are connected?** I used to use Server.app, and it would be easy to use that (or serveradmin on the CLI) to determine who was logged in. But since Server has been 'withdrawn', it doesn't seem so easy. I'm on Mojave. last |grep "logged in" gives: Ben ttys000 Sun Jun 7 15:24 still logged in Ben console Sun Jun 7 15:22 still logged in which doesn't seem to include current AFP connected users, as suggested by the recommended article. Nor does it give those connected to TM sharing or other connections; however, those can be gleaned from Activity Monitor. netstat -na |grep 139 just gives me a bunch of IP6 addresses. tcp6 0 0 fe80::18cf:f908:.51390 fe80::cab:3d08:d.61984 ESTABLISHED tcp6 0 0 fe80::18cf:f908:.61391 fe80::cab:3d08:d.61898 CLOSE_WAIT tcp6 0 0 fe80::18cf:f908:.54029 fe80::cab:3d08:d.61394 CLOSE_WAIT tcp6 0 0 fe80::18cf:f908:.64954 fe80::cab:3d08:d.56139 CLOSE_WAIT tcp6 0 0 fe80::18cf:f908:.50799 fe80::cab:3d08:d.51394 CLOSE_WAIT tcp6 0 0 fe80::18cf:f908:.52279 fe80::cab:3d08:d.61394 CLOSE_WAIT 6f249e60a5b12c27 stream 0 0 0 6f249e60a5b1396f 0 0 6f249e60a5b1396f stream 0 0 0 6f249e60a5b12c27 0 0 The best I've found is: netstat -f inet -n | grep '.548 ' | awk '{ print $5 }' | sed 's/\.[^.]*$//' which gives me IP4 addresses for all connections except SMB. Ideally, something that lists the connection type and username would be ideal, but it does seem that this is going to require a script rather than a one-liner.

I am having a problem copying certain directories and files from my Mac to my family file server via AFP. When I attempt to copy them by dragging them from a Finder window on my Mac to the corresponding Finder window on the file server, Finder displays a window saying, 'Copying 2 items to "other_folder"'. Then the copy hangs. - If I click the (X) icon to the right of the progress bar, the window adds a message, "Stopping…", but hangs forever. - If I attempt to eject the server volume from Finder, Finder refuses, saying, "The volume can't be ejected because it is currently in use." - The command ps up 670, where 670 is the process ID of the /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder process, says that the state of the Finder process is U. This "marks a process in uninterruptible wait", according to man ps. - I have narrowed down the problem to the point where I can trigger it by trying to copy only one directory containing only one file. Both directory and file seem innocuous: not very large, created in a very ordinary way. Sometimes I can recover from this by relaunching the Finder process, and after a couple of minutes the Finder relaunches in a new process, without the server mounted. Sometimes the Finder does not relaunch, and I have to log out and back in again, or even restart macOS. If I connect to the family file server via SMB rather than AFP, Finder copies the very same files with no problem. But I prefer to connect via AFP, because I make heavy use of relative symbolic links between my project directories. Neither Apple's SMB software nor the server's SMB software present symbolic links as links. Instead, they present links as conventional directories. That messes up my workflow. I have used this file server for years, and this Mac and its predecessor with this server via AFP for years. I have not encountered this problem before. I have copied similar files from Mac to server before without problems. Connecting to this server via AFP works well in general, even though both Apple and the server vendor have deprecated AFP. Hypotheses: - There is something about these files which triggers a bug in the Mac's AFP code. - Something in a recent macOS upgrade broke this aspect of AFP support. - Something about the path length or other context is the actual trigger, not the files themselves. - It is not the visible file, but an invisible system file like .DS_Store, which triggers the problem. The Mac is running macOS Sonoma 14.7.4, and has an Apple M1 CPU. The server is running TrueNAS-13.0-U6.2 software, with AFP support via NetATalk. How can I fix this so that these file copy operations succeed when copying via Finder over AFP? How can I recover from the hung Finder file copy in a less invasive way than restarting macOS? Can I interrupt a process in state U? How can I diagnose what is triggering the problem, so that I know to avoid it?

The file sharing dialog has confused me in every version of macOS I've used so far (Mojave, Ventura, Sonoma...) and I would like to understand the situation better. In advanced sharing settings (System Settings > General > Sharing > File sharing (i) > Options...) there is a concept called "Windows File Sharing" or "Windows sharing" that, for some reason, appears to be treated separately from simply "SMB sharing". #### Question By "Windows sharing", is macOS referring to something **distinct from SMB sharing?** I can't but conclude that it is, but **what then, more concretely, is this referring to?** I would've thought that the two terms "Windows sharing" and "SMB sharing" were generally used synonymously -- especially in an Apple context. I guess that in other words I'm asking: In macOS, does SMB sharing *without activating Windows sharing* imply "SMB sharing *with other Macs only*"? I find it difficult to tell, and so I can't adjust my expectations accordingly. ### Background I have many SMB clients that I currently have no idea what to expect from. For example: - Debian 13 - Ubuntu 24.10 (same client as Debian most likely) - Windows 10 - App-integrated SMB client libraries (like Kodi 21, and some iOS apps) None of them appears to be able to access macOS SMB shares without "Windows sharing". Should any of them work? I can't tell. Compound this with that I can access macOS SMB shares from other macOS systems, and it's clear that the shares do work -- just not for any OS but macOS (and, sometimes, iOS). ##### Forget about it Why not just enable "Windows sharing" and forget about it? Because... - I still wouldn't understand the situation, which I want to do. It suggests a gap in my knowledge that I would like to fill. - It gives me the impression that my non-macOS SMB clients are configured to be needlessly insecure. This suggests that they might not be configured properly, period. I'd like to find out if this is the case. - If storing passwords "less securely" is not a noteworthy detail, then surely Apple wouldn't have bothered to clutter their UI with the note. Therefore I can assume it's worth finding out more. *My knowledge level is: "Not an SMB expert" -- I have at most enabled some vfs modules in Linux Samba configurations (e.g. to allow TimeMachine to use shares as targets, and allow iOS to copy files to a share). I'm not familiar with its deeper intricacies.*

What it says on the tin. I hate the delay in the file icon appearing in the message field because it's preparing a version the sender and recipient(s) can collaborate on, and I hate having to manually change the dropdown-menu option from "collaborate" to "send a copy". Is there a way to change this behaviour, even if I have to delve into system files or Messages app resource files to do it?

I would like to enable logging on my file sharing service. (It's crashing intermittently and I can't figure out why.) When I inspect the plist for the file sharing service **smbd** on my Mac running Mojave, I see: user@mac:~ $ plutil -p /Library/Preferences/SystemConfiguration/com.apple.smb.server.plist { "AclsEnabled" => 1 "DOSCodePage" => "437" "LocalKerberosRealm" => "LKDC:SHA1..." "LogLevel" => 0 "NetBIOSName" => "transom" "ServerDescription" => "Transom" "SigningRequired" => 0 } So, it looks like logging is configured with the parameter "LogLevel". I've read the smbd man page, and it's not much help, with this parameter. - What are the allowed log levels? - Which level is best for debugging **smbd** crashes? - What's the preferred method for tweaking a value? (plutil can set, or...)

I need to copy some files from a RDC PC to my MAC. I can copy files from RDC to a PC but not to a mac. How can I do this? Thanks

Using macOS Sonoma 14.7.1 on MacBook Air M1, I want to share a specific folder with my Linux desktop (Linux Mint 22). I have enabled file sharing in macOS and I've set the password for a specific user: On Linux though, I can access all the user's home directory, the main hard drive not just the folder I wanted to share. **How can I limit sharing to a specific folder (i.e. Downloads)?**

I want to transfer files from my early 2015 MacBook air to 2020 M1 MacBook air. Connected with the USB-A to USB-C cord. Tried using target disk method through system preferences. 2015 model goes into target disk mode but M1 MacBook does not show it. Is there any troubleshooting required, or is it not possible to transfer files through this method?

I have a newer Mac (*MacBook Pro 2019*) and an older one (*iMac 2011*). For many reasons having to do with the fact that neither computer is compatible with the entirety of my software and devices, I often have to transfer files back and forth. **Box** or **AirDrop** work with more or less success but are generally slow and limited. Where it gets difficult, or impossible, is when I want to transfer open app pages of a document I'm working on (think for example of a RTFD document that I want to keep working on on the other computer because it has pictures I want to add), or browser pages with tabs. I was thinking that it would be amazing to be able to drag and drop these from one computer to another on the same network, the same way adding a slave screen to a Mac does, with the only difference that each computer would have its own OS. Is there a way to do that? ---- **Note**: *I have heard of Handoff, but I am not sure it handles tabbed browsing, and not sure if it will replace existing windows on the target device. I would rather select what I am sharing with each device by dragging it, rather than enable sharing for everything across both devices.*