July 19, 201312 yr I'm trying to setup an NFS share for ESXi so that ESXi can make automated backups of my VMDK's. I can mount and read/write to the share under ESXi if my unRAID rule for that NFS share is set to: *(rw) However, if I change that rule to: 172.30.0.61(rw) The share becomes inaccessible on ESXi. That's the IP address of ESXi. If I use the IP address of my Mac and use: 172.30.0.51(rw,insecure) I can then access the share via my Mac without any issues. Any ideas on what the issue could be or where I can start to troubleshoot?
July 19, 201312 yr Author Just to add, I've tried using: 172.30.0.61(rw,no_root_squash) However, I still can't connect to that NFS share from ESXi with that setting.
July 21, 201312 yr Author This doesn't look like an unRAID issue. From my testing it appears to be an issue with restricting IP's to machines running under ESXi. For some reason, my ESXi guest machines can't connect to NFS when I restrict the connections to their IP address'. If I instead use their DNS names as the restrictions, things work fine. I can also restrict to my Mac's IP and my Mac can mount the NFS share fine as well. So something funky is happening at the ESXi level regarding IP's. Does anyone have any thoughts on what that could be?
Archived
This topic is now archived and is closed to further replies.