Can't Use NFS to Access Home Shares

wagb4 wrote:
The NAS software appears to want UID values starting at 101, and Linux starts UID values at 1000. Assigning UID value of 1003 on the NAS to a new user is, I'm guessing, beyond the range of valid (usable) UID values on the NAS, at least for NFS. The NAS gives no indication that the UID value of 1003 is bad or not usable for NFS.

Private home shares are created when the user first logins using samba. After the first login using samba if the user logs out then logs in again the user should see the private home share.

wagb4 wrote:
The only ID value that matches between the computer's Linux and NAS OS is the GID value for group named "users", that is 101. I checked the computer's passwd and groups files and the Users and Groups listed in the code block agree with my Linux system, as expected. not even root can access those folders, or make changes such as chown or chmod.

I think for home shares using samba would be better for administrative tasks. The admin shouldn't write to another user's private home share (as that may cause ownership/permissions issues)

wagb4 wrote:
I believe UID values can be set in a configuration file on the server (NAS) but that would require using SSH, which NetGear says can void getting future support. I also think NFS supports UID:GID transalation but I am not sure that can be done on the client side, but only on the server (NAS) side, again the SSH warning enters the picture. I'm still researching this.

If you mess things up using SSH then you may be denied support, but it does depend on what you do. For some problems caused by SSH, help may be provided for a fee, but it does depend on what's happened.

Also note that some configuration is automatically repaired based on values stored in our readynasd database.