When you created the shared folder on Windows, you had the opportunity to change the default permissions on the share (which grants Everyone read-only access). You should go back to the share properties, and click on Permissions and grant Full Control permission to one or more Windows users known to your machine. Or you can give Everyone Full Control (but be careful what data you expose).

When you access the share from another machine (even a Mac) you should be required to authenticate with the Windows machine, at which time you would enter a username/password for a user known to the Windows machine. Then you will have write access.

Answer from Fran on Stack Exchange
🌐
Apple Community
discussions.apple.com › thread › 254603764
Unable to write or read file from SMB sha… - Apple Community
February 3, 2023 - On your Mac, choose Apple menu > System Settings, click General in the sidebar, then click Sharing on the right. (You may need to scroll down.) Turn on File Sharing, then click the Info button on the right. Click Options, then select “Share files and folders using SMB.” If you’re sharing ...
🌐
TrueNAS Community
truenas.com › forums › archives › freenas (legacy software releases) › freenas help & support › sharing
SOLVED - Unable to write to root directory of SMB share on macOS | TrueNAS Community
April 24, 2019 - Before you remove it, can you post output of the following getextattr -qq user DOSATTRIB /mnt/storage/persistent/clients | b64encode - My best guess is that the DOS readonly attribute is set on that share. You can remove the DOSATTRIB xattr through the command rmextattr user DOSATTRIB /mnt/storage/persistent/clients ... Short version of this story is that MacOS SMB clients interpret the DOS readonly bit in a non-standard way.
🌐
Reddit
reddit.com › r/openmediavault › cannot write to smb/cifs share from macos?
r/OpenMediaVault on Reddit: Cannot write to SMB/CIFS share from MacOS?
January 5, 2025 -

So i've had OMV running for a long while and never had any issues until early last year when I moved my main office PC to a MacMini. For some reason, I can read from my SMB/CIFS shares without any issues, but when I go to write to the share it locks up and says I don't have permission to write to the share. My user has no issue on my Windows or Linux machines with both reading from and writing to the share, and my Mac has no issue interacting with the SMB/CIFS share on my Synology.

Any thoughts what might be causing this? Is there a special permission that needs to be set on OMV for MacOS to read/write from the shares normally?

edit - idk what year it is anymore

Running OMV 6.9.8-1 (Shaitan) with all drives formatted to ext4, some of which are in a MergeFS pool together (but all drives have this issue, MergeFS or not).

🌐
Reddit
reddit.com › r/unraid › no write permissions smb/mac
r/unRAID on Reddit: No write permissions SMB/MAC
June 22, 2017 -

So I'm signed in to one of my unRAID SMB shares on my mac using an account that's set to 'Read/Write access in the share settings.
Now most of the time when I try to rename anything on the share using my MAC I get an error saying that I don't have the permission to do so.
Why is this happening when I'm using an account that should have full Read/write access ?

🌐
GL.iNet
docs.gl-inet.com › router › en › 4 › faq › macos_cannot_write_samba
MacOS cannot write to a Samba share - GL.iNet Router Docs 4
Log in to your router’s web Admin Panel, and verify the shared folder has "Read/Write" permissions enabled for your user account. Use the cp -X file-name command to copy the file. Since Finder automatically adds extended attributes (e.g., resource forks, metadata) during transfers, which ...
Find elsewhere
🌐
Apple Community
discussions.apple.com › thread › 2382501
No rights to write on SMB mounted volume … - Apple Community
None of the accounts used have admin rights to the smb share. All I can suggest at this point is to review the console logs and the Event viewer logs if on a Windows server. I will be monitoring for any issues in this area as we are a cross platform environment with users on Mac OS and Windows XP with both Mac shares and Windows shares with dedicated servers for both.
Top answer
1 of 1
5

Looks like you created a folder miguel in the media and you have taken ownership of it. Instead, let's create a group, add users to that group, and set the permissions.

sudo groupadd -g 10000 [samba_group]
sudo adduser migeul [samba_group]
sudo chown root:[samba_group] -R /media/migeul
sudo chgrp [samba_group] /media/migeul
sudo chmod 775 -R /media/migeul

This will create a group and attach it to the folder to be shared. You add the users to that group for access. Set the permissions to 775 which gives the owner and the group read-write-execute access while others only read. Set's it recursively.

Verify that you have total access to the folder. With samba, setting the permissions are a little bit different than file permissions with a ubuntu user. What I mean is that verify the permissions after you take ownership because they could result in a samba error later on down the road. Where nobody can access the drive.

Create a samba account that matches your Linux username precisely.

sudo smbpasswd -a miguel
sudo smbpasswd -e migeul

That will prompt you to create a password for the username miguel. Please note that this is only for SMB shares not for the user in the Operating System.

Afterward, open up the samba config and when sharing the drive make sure you type in writable = yes, browsable = yes, read only = no and add your group to it as well. Also, verify the location you are sharing from. Use the place that it is mounted to.

[migeul]
comment = Migeuls folder
​path = /media/migeul
​browsable = yes
​writable = yes
​guest ok = no
​read only = no
​valid users = @[samba_group]

After you reconfig the /etc/samba/smb.conf file, reload it.

sudo smbd reload

These pages go more in-depth with setting up samba shares.

https://help.ubuntu.com/community/Samba/SambaServerGuide https://www.techrepublic.com/article/how-to-set-up-samba-shares-for-groups/

You may also need to set your umask as well. To do that open up /etc/profile using sudo nano /etc/profile and at the bottom type in umask 002. Use Control+O to save and Control+X to exit. Best to reboot the server using sudo reboot and the new mask permissions will take place. That setting re-asserts the same permissions for the users.

🌐
Apple Community
discussions.apple.com › thread › 5307720
can not write to my smb share from mac os… - Apple Community
September 16, 2013 - The mac clients are binded to the domain an i can read/edit file permissions from the mac client and also have acces to the network users (from Directory Utility). My issue is that i can acces the smb shares but not write to them. the file permissions regarding the users seems to be ok as my test user have read/write acces to the share.
🌐
Marriott Library
apple.lib.utah.edu › mac-bug-connecting-to-non-apple-smb-shares
Marriott Library - Apple Infrastructure | Mac Bug Connecting to Non-Apple SMB Shares
June 29, 2025 - We have been informed this is an Apple issue, but we have no timeline to share for a fix. We hope Mac OS 10.13 High Sierra will include it. For 10.13, can you try disabling FileIDs (in /etc/nsmb.conf ) until you can deploy macOS Mojave? ... Let us know if this works around the issue in High Sierra. apple, bug, file sharing, microsoft, OS X Server, SMB
🌐
MacPaw
macpaw.com › how to › tips & tricks › guides
Mac file sharing is not working? Here are 4 tips to try
August 12, 2025 - Enable file sharing on Mac with Terminal. Instead of going to System Settings, you can use Terminal to enable file sharing. Open Terminal from Applications > Utilities and run these two commands: sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.smbd.plist · sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server.plist EnabledServices -array disk
🌐
OS X Daily
osxdaily.com › 2010 › 05 › 02 › simple-fix-for-mac-os-x-10-6-3-samba-write-access-problem
Simple fix for Mac OS X 10.6.3 Samba Write Access problem
May 2, 2010 - This is why the fix works, you are disabling unix extensions (of course, you could disable wide links but there is a performance hit to that method) and the error will no longer occur. I imagine this is just a bug in the way that Mac OS X 10.6.3 handles SMB shares and it will probably be fixed relatively quickly by Apple, and when it is fixed you can and should reactivate unix extensions again on the Samba server.
🌐
MacRumors
forums.macrumors.com › macs › macos › macos
Can read but cannot write to windows servers | MacRumors Forums
February 7, 2008 - We use the Windows server "services for macintosh" plug-in, which allows us to use AFP rather than SMB, but it _should_ work perfectly well either way. If you are on an AD domain, you don't actually _have_ to have AD login set up on your mac, but you DO have to authenticate correctly against the domain when mounting shares. In addition, you must have a corresponding account set up in AD to authenticate against, and it must have the correct read-write permissions set against the directories concerned.
🌐
MacRumors
forums.macrumors.com › macs › macos › macos
After 10.6.3: Cannot write to SMB network drives anymore | MacRumors Forums
March 31, 2010 - You are right - when i tried the unix extensions off earlier, I'd amended smb.conf in the section that related to the specific share. I moved the "unix extensions = no" entry into the [global] section of smb.conf, restarted samba and everything works well. Phew and thanks! Of course, since the server is mine to control and setup, this fix is OK - not sure if campus wide servers would be amenable to such a change. VMT Bob · You must log in or register to reply here. ... Register on MacRumors!