Some caveats: - NFSv3 does not support references to Windows users/groups that aren't mapped to equivalent Unix users/groups.
- NFSv4 and SMB, on Solaris Express / Nevada / OpenSolaris, do, but when it comes to NFSv4 it also matters whether both, the client and server can do it. - So if you must use NFSv3, or if you must use NFSv4 clients other than Solaris Express or Windows-based NFSv4 clients, then you need to consider name-based mapping rules or directory-based mapping. You already indicated that you have equivalent Unix entities with the same exact names for all the relevant Windows entities, so all you need is the name-based mapping rule that you said you already created, and mixing NFSv3 and SMB should work just fine for you. Making sure that you had the same names on both sides shows good planning on your part. Congratulations :) (IIRC there are still some issues with file locking + mixed protocol access, but I'll let someone else address that.) Nico -- _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
