On 08/29/11 21:28, Marc Bevand wrote:
So are you saying I should try after "sharectl set -p nfsmapid_domain=any-other-name.com nfs" and ownership should be handled correctly? I will try tomorrow.
That might work. What *wouldn't* work in that configuration was any user that was only a UNIX user and was not a Windows user.
Although this particular interaction (NFSv4 and AD) has some rough edges, it *is* at least a bit sensible. Domains define a space where a particular set of names is known. Your NFSv4 domain name setting says which domain your UNIX user names are known in. If you use the same names for NFSv4 and AD you are in a sense saying that the names are the same between the two, and normally (absent either setting the UNIX name service to use LDAP from the AD servers, or manually synchronizing the databases) that wouldn't be the case. The best thing to do to make that work right is to set the UNIX name service to use AD LDAP, so that everybody in that domain is using the same directory.
_______________________________________________ cifs-discuss mailing list cifs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
