Dan,
I changed the permissions on the /data folder like you specified above, but I still cannot access /data from windows. Here is what the permissions are set as. Do I need to specify an AD user/group as owner of that folder? Does the smb.conf look ok?
drwxr-xr-x 30 root root 34 Jul 22 12:51 .
drwxr-xr-x 30 root root 34 Jul 22 12:51 ..
drwxrwxrwx 21 root root 21 Jul 30 08:00 data
I agree with you that it sounds like it is a permissions issue on the Solaris box itself. When I try to SSH with an AD account, after 6 password attempts it responds with " Server sent disconnect message type 2 (protocol error): "Too many authentication failures for 'username' " I was able to lock the account on the domain earlier, but now it isn't locking it out, even if I enter a gibberish password. If I do kinit 'username' and enter a gibberish password, it shows badpwdcount 1 on the domain. So it might be something in PAM.conf that isn't using winbind for SSH.
Any other thoughts or ideas? Thank you for your time thus far, I truly appreciate it.
Main Topics
Browse All Topics





by: it4sohoPosted on 2009-08-03 at 09:05:40ID: 25005687
OK, you've described 2 different errors:
1) Inability to browse samba files from an AD account on a Windows client
2) Inability to login to a Solaris system with an AD account
I believe that the two errors are unrelated.... and both trace to either permissions or configuration behavior.
1) You've said that wbinfo -u and wbinfo -g show valid results, which shows that you've joined the domain and are correctly getting data from the AD server -- so the issue appears to be one of permissions on the Solaris system.
Your share folder is /data -- please ensure that world execute permission is ON for the root folder, and that both read & execute permissions are enabled for all users on the /data folder:
# the output below CAPITALIZES the permissions we CARE about -- you will NOT see CAPITAL letters!
ls -al /
drwxrwx--X 20 root root 4096 Mon dd HH:MM .
drwxrwx--X 20 root root 4096 Mon dd HH:MM ..
...don't care
dRwXRwXRwX 20 user group 4096 Mon dd HH:MM data
...don't care
NOTE: I don't care about write permission on /data because it IS valid to have a read-only share! PROBABLY not what you want, but you didn't specify....
2) You've said that repeated failures to login to the Solaris system with an AD account will result in the AD account becoming locked by the AD server. This indicates that the login credential passing is working correctly, and it is the login process itself that is failing -- I suspect that it may be because of permissions on the default login directory. Since the AD user won't have an entry in /etc/passwd, the login (or ssh) system will have to have them login to the / folder -- and, as with the above, they must have both READ and EXECUTE permissions on this (root) folder for login to complete. (Of course, you could have changed the default login path in a number of ways -- in which case, check the permissions to that path).
I hope this helps!
Dan
IT4SOHO