I'm a newbie when it comes to Samba but oddly enough I can access a Samba share via a networked client (windows/linux etc) but I cannot access the folder as the same account when logged in via SSH. I thought local perms were easier than Samba.

FC6 is the distro.

Samba is setup with ADS and KRB5. Authentication works as I can log in as root with local passwd or with my AD account with my AD passwd. The folder is called projects and it's under the home directory. (/home/projects). Root can access this folder naturally and if I chown to my account, then I can access it. The home folder and all sub folders are rxw for a group called 'test' which I am a member of. I even ran "setfacl -m g:"DOMAIN+YourGroup":rwx /home" with the proper AD group and domain, and that doesn't help. I'm certainly missing a crucial step. Thanks in advance.

Lets clarify a few things

Are you using Nautalus, Konqueror, WIndows host? HOw are you able to access and with what user?

Check your 'unix' account and see if the correlation is built between it an Samba and that that user is in a group allowed access. Odds are this is where the issue lies.

1) Check what users are allowed to the share as defined in /etc/samba/smb.conf
http://www.faqs.org/docs/securing/chap29sec284.html
Example:
[homes]
comment = Home Directories
browseable = no
read only = no
valid users = joe bob jane

2) Check what user relationships are defined between 'unix' and 'samba'
Example:
[root@wizej samba]# cat /etc/samba/smbusers
# Unix_name = SMB_name1 SMB_name2 ...
root = administrator admin
nobody = guest pcguest smbguest
test = TEST

3) As for the use of ACLs in Linux. They do not correlate to the permission which samba uses like you would expect if you were a Windows Admin. I have never personally used Linux ACLs on a box as 99% of file permissions are sufficient with basic unix file perms. Your ability to access the files (please define 'access',,.....read, write, view ect) in on tool and not another is likly as you stated, something crucial, but also likly something simple.

I found my problem. Thanks for the reply all the same. I think it has something to do with ADS permissions and Unix permissions getting mixed. Here's is how I fixed it.

I deleted the folder, re-created it, chmod to 777, re-applied the rights for winbind using (setfacl -m g:"DOMAIN+group":rxw foldername) and then it works, both from a Windows XP box and also from the shell.

The problem will re-occur if I were to add local unix groups to the same folder. So if I were to type "chgrp groupname foldername" it would break right away. Must be a link between locals groups and ADS groups and I missed that step.

Thanks!