So, in this case, we’re only using the SMB client portion of SAMBA, as opposed to the server, but it’s working perfectly. Just installing the SAMBA package on another 10.10 machine did not fix the issue, presumably because the SMBUp installer disables the Apple SMB components as part of its multi-step installation and configuration process (which is really awesome, btw).
Smbup similar full#
I installed the full SMBUp package on two different machines (one 10.10 and one 10.11) and it completely fixed the Photoshop write access issue on both.
Why not just stick with AFP then? Well, we found that SMB is much faster when working off the NAS in InDesign AFP seems to cause sluggishness whenever InDesign does auto-saves, and it’s really irritating. And saving usually requires stoppping/starting the service. change requires saving the configuration (as it’s a single file). Selecting a share and pressing the “delete” key removes them.As you noticed.any. The FAQ contains steps to create one of these “Sharing-only users”.Dragging folders onto the list can add them quickly. In those cases SMBUp will complain that a specific user can’t be used and a new one should be. Since the application checks for version updates I have a rough idea of its usage and installations and the lack of donations became the main reason no further updates to SMBUp were made after the current (stable) one (which is the point when the application became 100% useable for me, so I don’t need added functionality for it).On adding users: In some rare cases OS X has the existing users with a recursive tree of groups that makes Samba choke.
This means that, with any luck, SMBUp won’t be necessary in the future for anyone:) -I truly appreciate reminding people this is donationware.