malum-in-se
Dabbler
- Joined
- Nov 6, 2014
- Messages
- 19
Thanks to anyone who can take the time to help me with this. I'm about 15 hours into researching and still can't what I need accomplished.
Problem: I have Windows 10 Pro with Client for NFS installed. I log into my windows box with User "Bob" and "normal_bob_password". Once logged into that Windows box, it properly mounts several Mapped Samba shares with the appropriate permissions of the user who logs in. There is a separate NFS, of completely separate data set. A bunch of "nix boxes access that share as read only. However, the "Bob" windows 10 box, needs to have full control over that data set. Client for NFS is installed. Currently that mapped drive can be mount, and searched, however it mounts as user -2, (anonymous) and doesn't have write permissions. The ownership of those files, as well as the Freenas user is not "Bob", it is "Bill", and cannot be "Bob". Using credential manager to mount and map it the appropriate user on the Freenas side has been unsuccessful. I do not have AD or LDAP, nor do I want it.
Setup: Freenas 9.3, Windows 10 Pro, Pfsense 2.3--Runs unbound DNS resolver. The domain is bobhome.dev.
Questions:
1. Supposedly user mapping can be set locally via passwd and group files in Windows. What is the proper format for those files, and how can I ensure that is where the client is mapping to?
2. Somewhere my NFS mapping is getting sideways. It connects to the NFS share always, but the mapping is always off. Under credential manager I have tried 100s of combinations of bill@bobhome.dev, bill, 1009 (bill freenas UID), NAS/Bill (Nas is the Samba netbois), freenas.bobhome.dev/Bill... nothing . I've tried setting the share address as freenas.bobhome.dev. I've tried setting it as the IP: 192.168.1.130. Both of those will connect, but none of them map correctly.
3. What logs should I be referring to, to specifically see how the mapping is going and where it is breaking down?
4. Any input on specific settings would be great. i.e enable NFS4 etc.
5. When using credential manager in Windows 10, what is the proper format under "user" for a Freenas 9.3 NFS share? Is it domain\freenas User, or freenasuser@domain.com?
6. What is the best command on the freenas CLI to see as what user/group shares are being mounted as? What about on the Windows 10 side? I've begun learning all the nfsadmin powershell commands but that's an entirely new world for me... last time I used windows at a command prompt was Windows 3.1.
Thank you again for anyone who can offer their time to help.
Problem: I have Windows 10 Pro with Client for NFS installed. I log into my windows box with User "Bob" and "normal_bob_password". Once logged into that Windows box, it properly mounts several Mapped Samba shares with the appropriate permissions of the user who logs in. There is a separate NFS, of completely separate data set. A bunch of "nix boxes access that share as read only. However, the "Bob" windows 10 box, needs to have full control over that data set. Client for NFS is installed. Currently that mapped drive can be mount, and searched, however it mounts as user -2, (anonymous) and doesn't have write permissions. The ownership of those files, as well as the Freenas user is not "Bob", it is "Bill", and cannot be "Bob". Using credential manager to mount and map it the appropriate user on the Freenas side has been unsuccessful. I do not have AD or LDAP, nor do I want it.
Setup: Freenas 9.3, Windows 10 Pro, Pfsense 2.3--Runs unbound DNS resolver. The domain is bobhome.dev.
Questions:
1. Supposedly user mapping can be set locally via passwd and group files in Windows. What is the proper format for those files, and how can I ensure that is where the client is mapping to?
2. Somewhere my NFS mapping is getting sideways. It connects to the NFS share always, but the mapping is always off. Under credential manager I have tried 100s of combinations of bill@bobhome.dev, bill, 1009 (bill freenas UID), NAS/Bill (Nas is the Samba netbois), freenas.bobhome.dev/Bill... nothing . I've tried setting the share address as freenas.bobhome.dev. I've tried setting it as the IP: 192.168.1.130. Both of those will connect, but none of them map correctly.
3. What logs should I be referring to, to specifically see how the mapping is going and where it is breaking down?
4. Any input on specific settings would be great. i.e enable NFS4 etc.
5. When using credential manager in Windows 10, what is the proper format under "user" for a Freenas 9.3 NFS share? Is it domain\freenas User, or freenasuser@domain.com?
6. What is the best command on the freenas CLI to see as what user/group shares are being mounted as? What about on the Windows 10 side? I've begun learning all the nfsadmin powershell commands but that's an entirely new world for me... last time I used windows at a command prompt was Windows 3.1.
Thank you again for anyone who can offer their time to help.