Solved

Unable to write to NFS datastore in Vcenter

Posted on 2014-03-19
12
834 Views
Last Modified: 2014-03-25
Hello all,
I am having an issue with an NFS datastore within Vcenter. I have a NFS share on a Win2k3 server which I am able to successfully mount. However.. I cannot write to it even though the permissions seem correct.  This server is hooked up to an EVA Storage vault drive array with 2TB of storage.

It looks like it's not listing the contents either as when I try to mount it, it shows as 0.00B capacity.. and I know there are files in that NFS datastore. From this same host, I can mount other NFS datastores successfully.

Please help.. been at this for 2 days banging my head on my desk! :(
Esxi-nfs-permissions.jpg
NFS-Permissions.jpg
NFS-Storage.jpg
0
Comment
Question by:kjs00333
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 6
12 Comments
 
LVL 62

Expert Comment

by:gheist
ID: 39939772
By default ESXi alows to mount 8 NFS volumes.
0
 

Author Comment

by:kjs00333
ID: 39939798
Thanks for your reply gheist, but I have no idea what that has to do with what I'm asking..
Mounting the NFS volume is not the issue here.. permissions seem to be, and I'm not sure where it's going wrong.
0
 
LVL 62

Expert Comment

by:gheist
ID: 39940651
Windows has security log 3 clicks away to log all permission problems.
Size 0 on unix means that you could not connect nfsd, only mountd, if that helps..
0
U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

 

Author Comment

by:kjs00333
ID: 39940668
It sort of makes sense since that's the problem I'm seeing but I don't know how to resolve this with server 2k3. Can you elaborate a bit more?  I'm a bit new with Unix and NFS.  With server 2008, I did not have these issues with permissions.
0
 
LVL 62

Expert Comment

by:gheist
ID: 39940687
In 2008 firewall is per-program, in 2003 per-port
so make sure all these are open:
http://support.microsoft.com/kb/891760
0
 

Author Comment

by:kjs00333
ID: 39940914
There is no firewall active on the server.  I have the service completely disabled.  I am more curious about the Unix NFS stuff as that seems to be the real issue here.
0
 
LVL 62

Expert Comment

by:gheist
ID: 39941075
You run windows and vmware, no idea where you halucinate about unix,
And "disable firewall" does not work in windows server. once you open control panel of firewall it comes back.
0
 

Author Comment

by:kjs00333
ID: 39942116
The windows firewall is not running. The ICS service is completely disabled. It will not even open up in control panel. You can telnet to this box on all necessary ports. So the firewall would not be the issue here.

You said "Size 0 on unix means that you could not connect nfsd"  That is what I believe the problem is, and I do not know what the fix is on Win2k3.  My server 2008 datastores do not have this problem because I can use No Server Authentication with Unmapped user access on NFS shares.  

Screenshot attached.
unmappeduseraccess.jpg
0
 
LVL 62

Expert Comment

by:gheist
ID: 39942347
And what are the access permissions over network, for root user as vmware uses?
0
 

Accepted Solution

by:
kjs00333 earned 0 total points
ID: 39942403
Fixed it.  In server 2003, there is a local security policy which was overriding the NFS anon permissions. It's located under  
Computer configuration > Windows Settings > Security Settings> Network access: Let Everyone permissions apply to anonymous users


I did a gpupdate /force once the change was implemented, enabled anonymous user access with the GID and UID of -2.  Root access enabled as read / write from all machines. Now my datastore is showing up, and I can read and write to the drive as intended.
0
 
LVL 62

Expert Comment

by:gheist
ID: 39942442
Actually vmware uses only root to access nfs, so it should not matter if you use anonymous mapping or root remapping to nobody or so. It will keep working as long as it can create file...
0
 

Author Closing Comment

by:kjs00333
ID: 39952714
Resolved after much frustration.
0

Featured Post

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Many businesses neglect disaster recovery and treat it as an after-thought. I can tell you first hand that data will be lost, hard drives die, servers will be hacked, and careless (or malicious) employees can ruin your data.
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …
This Micro Tutorial walks you through using a remote console to access a server and install ESXi 5.1. This example is showing remote access and installation using a Dell server. The hypervisor is the very first component of your virtual infrastructu…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question