unable to write to CIFS shares after 9.2.1 upgrade - (N00b)

[Darkeyce]

I muddled through the various guides and had FeeNAS 9.2.0 up and running fine, Sharing 2 locations with my windows boxes via CIFS (yay).

Last night is i did an inplace upgrade to 9.2.1...stuff is now broken.
specifically;

• Shares are still visible but applications can no longer WRITE to them.
• Applications can still READ from the shares with no problem
• I still can create a folder or file via the windows explorer interface (i guess that's not broken but it is nice to know)
• I continue to get the warning about "share" value for the 'security" parameter.

I tried a few things, changing the store acl from unix to windows/mac, that took a while and produced an astounding number of 'getfacl' and 'setfacl' messages indicating files or folders were not found. I tried to messign with a couple of the CIFS parameters 'local user' to 'anonymous' for example...that also didnt work but is did lied these mesages that i think are the crux of my problem....
Feb 15 09:09:43 freenas winbindd[5943]: [2014/02/15 09:09:43.868154, 0] ../source3/winbindd/winbindd_cache.c:3183(initialize_winbindd_cache)
Feb 15 09:09:43 freenas winbindd[5943]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
Feb 15 09:09:43 freenas winbindd[5943]: [2014/02/15 09:09:43.869831, 0] ../lib/util/util.c:282(directory_create_or_exist_strict)
Feb 15 09:09:43 freenas winbindd[5943]: invalid permissions on directory '/var/db/samba4/winbindd_privileged': has 0755 should be 0750
Feb 15 09:09:43 freenas winbindd[5943]: [2014/02/15 09:09:43.869866, 0] ../source3/winbindd/winbindd.c:1579(main)
Feb 15 09:09:43 freenas winbindd[5943]: winbindd_setup_listeners() failed
I just don't know how to fix them...Not a *nix guy and have been faking it so far. this is just past my how to level.
So any step by step would be appreciated. If anyone else is experiencing the access problem I am and has a solution assuming the winbindd isn't it i'd appreciate their insights.

 

[Darkeyce]

Resolved my own issues...

Did some more research and 'chmod' is my frined. that was easy enough. I think that had some other ripple effect. I went to the permissions for my individual volumes to change them back to unix ACLs. I had to update the write permissions for group and other, but this time they "stuck" and access is now enabled for all people again.

Also had to change the owner from Root to my guest account...so maybe none of that other stuff did anything?

As soon as i can figure out how to change this to solved i will update the title