You can use the 'wcc' command, to verify if the correct unix-to-NT mapping is done for your users. It sounds like the filer doesn't seem to understand that UID 10025 should be mapped to NT user DOMAIN\jdoe.

There are some issues with using mixed style qtree's/volumes but they are laid out very well in your filer documentation / NOW. It's mostly the use of extended / group permissions in CIFS that doesn't carry over to NFS.

On 5/12/07, Michael Fahy fahy@chapman.edu wrote:

We have an FAS960 running NFS and CIFS. There are entries in the cifs_homedir.cfg file so that Windows users can map drives to their Unix home directories. Windows users can successfully map drives to their unix home directories but unless their files and directories are configured with write permission for "everyone", (i.e. 666 permissions for files) the Windows users cannot write to their own files and directories. The filer is not successfully matching the Windows username with the corresponding Unix username (even though the names are the same). We are using OpenLDAP for authentication on the Unix side. We have been told that "Files and directories created from unix using nfs only get their permissions read properly by other unix systems, and the same with cifs by Windows systems" but I do not believe this. I'm sure we are just not configuring the filer correctly. Any suggestions?

Your subject mentions "mixed" mode, but there's nothing about that in the post. Can you also verify the security setting of the qtree containing home directories? If they're not in a qtree, what's the security setting of the volume? "Mixed" mode generally refers to the mixed security mode on qtrees and volumes. Permisions can be set via both Unix and Windows, but they stomp on each other if you (and your users) are not very careful. We've found it's best to control security with one or the other and let usermapping (which you're having trouble with) handle the rest.

You can use the "wcc" command to determine what the NetApp is seeing as far as usermapping goes. "wcc -u <uname>" will show you the mappings it finds from the Unix uname to the Windows account. "wcc -s <ntname>" will show you the reverse (from Windows to Unix). This will at least tell you if you indeed have a mapping problem or it's somewhere else.

Jeff Mery - MCSE, MCP National Instruments

------------------------------------------------------------------------- "Allow me to extol the virtues of the Net Fairy, and of all the fantastic dorks that make the nice packets go from here to there. Amen." TB - Penny Arcade -------------------------------------------------------------------------

"Michael Fahy" fahy@chapman.edu Sent by: owner-toasters@mathworks.com 05/12/2007 03:29 AM

To toasters@mathworks.com cc

Subject Problems with mixed mode

We have an FAS960 running NFS and CIFS. There are entries in the cifs_homedir.cfg file so that Windows users can map drives to their Unix home directories. Windows users can successfully map drives to their unix home directories but unless their files and directories are configured with write permission for “everyone”, (i.e. 666 permissions for files) the Windows users cannot write to their own files and directories. The filer is not successfully matching the Windows username with the corresponding Unix username (even though the names are the same). We are using OpenLDAP for authentication on the Unix side. We have been told that "Files and directories created from unix using nfs only get their permissions read properly by other unix systems, and the same with cifs by Windows systems" but I do not believe this. I’m sure we are just not configuring the filer correctly. Any suggestions?