NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Saving Microsoft Word files to ReadyNAS from MAC
Apologies for not adding to the existing thread on this subject here, but it's closed, marked as Solved.
There is still an issue saving from Microsoft Word for Mac to a ReadyNAS SMB Share. Roling back the Word version, or using .doc files is a workaround as discussed in the previous thread, but it felt to me as if there is most likely a Samba misconfiguration on the ReadyNAS. The issue only occurs when 'Enhance MacOS' is enabled in the SMB service settings. This setting is automatically enabled if SMB Timemachine is used.
Eventually, I found this article on the Microsoft forums:
which contains a suggested update to the smb.conf file that fixes the issue. I'm no expert in Samba, so I couldn't tell which config setting gets it all going, but I've updated my conf file on the NAS and Microsoft Word for Mac can now save to the share.
The smb.conf extract is below. I've added this to /etc/smb.conf, at the end of the existing [Global] section, before the #includes.
I realise this may well get overwritten, as on the ReadyNAS smb.conf is automatically generated. When that happens, I'll find a better place to put it. Perhaps in /etc/frontview/samba/smb.conf.defaults. Not sure, more trial and error needed.
Not sure if the ReadyNAS devs read these forums. But if so, any chance of getting the config fixed in a future release please?
Good luck
Nick
[Global] # # PREREQUISITES TO FUNCTION WITH OSX # min protocol = SMB2 ea support = yes # # NOT NEEDED WITH OSX/LINUX # disable netbios = yes dns proxy = no smb ports = 445 name resolve order = host bcast # # GENERAL COMPATABILITY WITH OSX SMB # adds alternate data streams (ADS) support # vfs objects = catia fruit streams_xattr # # STORAGE OF OSX METATDATA & RESOURCE FORK # in Netatalk compat xattr & ._ AppleDouble File # fruit:metadata = netatalk fruit:resource = file # # FILE LOCKING # no cross protocol locking # fruit:locking = none # # # MAP NTFS ILLEGAL CHARS TO UNICODE # fruit:encoding = private # # SMB2+ AAPL EXTENSIONS # file metadata - Unix mode, FinderInfo, resource fork size, permissions # fruit:aapl = yes readdir_attr:aapl_rsize = yes readdir_attr:aapl_finder_info = yes readdir_attr:aapl_max_access = yes fruit:nfs_aces = yes # # OSX COPYFILE # fruit:copyfile= yes # # PERFORMANCE TWEAKS # note - error with smb2 leases # smb2 leases = yes kernel oplocks = no use sendfile = yes # # FILE CLEANUP # delete veto files = true unix extensions = yes fruit:posix_rename = yes # # PARAMETERS IN SAMBA VERSION > 4.3.11? # testparm does not check fruit parameters # fruit:model = MacSamba fruit:veto_appledouble = yes fruit:zero_file_id = yes fruit:wipe_intentionally_left_blank_rfork = yes # ## END OF ADDED CONFIGS #
1 Reply
Replies have been turned off for this discussion
If you want your changes to "stick", move them to /etc/frontview/samba/addons/addons.conf. That appears to be reserved for apps to make any necessary changes to smb.conf and is included in smb.conf via an include statement. My experiments show it survives an OS update or re-install, where changes to smb.conf do not and may not survive other things I've not tested. The file may not exist on your NAS, so create it. You do need to include the [Global] header. Since that include is near the bottom, anything in addons.conf can override what's in smb.conf because the last entry is followed if there are contradictory ones. That's a double-edged sword if you make a mistake. Of course, it's always a good idea to also keep another copy somewhere on your data volume in case you do ever need to restore it. It does get included in a configuration backup.
This sounds like something that the Mac compatibility option should add.
In the meantime, a configuration backup restoration could be an easy way to let those who are not comfortable with SSH implement this. A backup does not need to contain all the files -- the restore will add/overwrite whatever is there in the configuration .zip (at least if it's on the list of appropriate files, as this is -- I don't know about any others). So as long as there is not already an addons.conf that needs to be added to, that would work. NOTES TO ANYONE TRYING THIS: The file will need to be formatted for Linux -- EOL character is an LF, not CRLF, so you have to use the right editor if doing this from Windows. It also has to be in the right folder in the .zip, and upper/lower case will matter. Since file ownership doesn't get included in a .zip, I don't think you need to do anything there, but I've not tried it.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
