![smbup not starting smbup not starting](http://eduo.info/wp-content/uploads/2013/07/sharedprefsfolder.png)
They always have "custom access" when viewed from the Get Info panel on the local computer. Even so, most of the time, the ACLS are respected regardless of the POSIX and the user has proper permissions. However, when things go wrong nothing a local user does ever works. It seems that the clients are at that point ignoring the ACLs and relying solely on POSIX in these cases. If I try to fix it on the server end by modifying the permissions, that will sometimes allow the clients to then modify or delete the files, but in many cases, only a restart of the client computer will clear the problem, and in some cases, I have to move or delete the file on the server end. While this behavior is WAY more common on the El Crapitan clients, it does also happen on Yosemite.
![smbup not starting smbup not starting](https://i.ytimg.com/vi/PAhoEoLarhg/hqdefault.jpg)
When the problem becomes a very common occurrence, what I do to mitigate the nightmare is to strip the ACLs from the shares and all child folders about twice a month and then set the posix permissions to 777 in Terminal.Then I go back to the Server App, and set things up as 775 again and then add in my ACL's and then finally propagate. This tends allow most things to function normally for a time, but I eventually get a few complaints here and there until the problem becomes very common again and I am back to the reset route. I have no idea why the stripping and replacing with the exact SAME permissions they had before (at least with the ACLs) works. So the issue I see at this point is that sometimes the permissions are being ignored, and the users see erroneous error messages about not having proper permissions to affect files. This happens on the clients despite verifying that the permissions are set correctly as I have outlined them above. If I connect from a 10.8.5 based Mac, then everything works fine. This was also the case when the server and the whole network was using 10.8.5. The other wrinkle in this sad saga is that I can revert a client access to AFP instead of SMB it works flawlessly.