Woot! It worked. I changed the local security policy to the KB article, but then allowed anonymous access with the GID of -2 and UID of -2. Once that was done, it's now showing correctly in Vcenter and allowing me to read and write to the data store. Before I had it set to 0,0 even with the security policy change which didn't work. So hopefully this issue helps someone in the future and they don't have a hair pulling experience like I did.
WHAT A PAIN !
Anyways, thanks all for your time.
Thank you for your reply Grasshopper, but that solution does not apply to me as I am using Server 2003 R2. My screen shots above show the console.
I'll check / test this out and come back to you tomorrow.
I've found that the issue might be related to space concerns. Could you try by using a smaller disk size for the NFS share?
I actually tried on two different shares with two different disk sizes. One on a SAN, one on a local disk with the same problem.
One other thing I tried which was mentioned in a KB Article was to modify the local security policy of the server.
This was done and it did not correct the problem.
But if you can mount it, you have the required permissions to access it.
Woot! It worked. I changed the local security policy to the KB article, but then allowed anonymous access with the GID of -2 and UID of -2. Once that was done, it's now showing correctly in Vcenter and allowing me to read and write to the data store. Before I had it set to 0,0 even with the security policy change which didn't work. So hopefully this issue helps someone in the future and they don't have a hair pulling experience like I did.
WHAT A PAIN !
Anyways, thanks all for your time.