Hi all,
Hoping someone can shed some light on this for us as we're stumped.
We're trying to mount some volumes from our filer on a Windows box via NFS for the purpose of backing up the contents. We're trying to use NFS as we don't have a CIFS license and have no other need for one. The volumes in question store ESX Virtual Machines if that makes any difference.
Environment:
Windows 2008 Standard x64
FAS2050c
Connected directly via a private network
We've installed Services for Unix on the Windows box, which gives us the required to tools to mount an NFS export as a drive letter in Windows. On the SAN, we've given root & RW access to the IP address of the Windows box.
We then try to mount one of the exports via the command line:
mount -u:x -p:y
111.111.111.111\vol\test z:
This command completes correctly, and the drive letter appears, but we then run into permissions problems.
We can browse the contents of the drive, but cannot write any files / folders, nor read most files.
Looking at the NFS mount properties of the drive letter in Windows, it shows under "User authentication" a UID of -2 and "Primary GID" of -2.
Based on this, I assume our permission problem is something to do with the Windows box not properly authenticating with the filer, and ending up as an unpriviledge user? I can't find any references to UID or GID -2 on the filer or the net, so not sure where that is coming from.
We've tried fiddling with the export's security options (removing "root" option, adding "anonymous ID" option) and also creating a completely seperate user on the filer with administrator priviledges and connecting as that user from the Windows box - nothing works. No matter what we do, the UID and GID stay as -2 on the drive properties, and we have problems reading / writing data.
Any ideas?