silverbullettruck2001
Dabbler
- Joined
- Jul 20, 2014
- Messages
- 22
I have been looking for a resolution to this issue, but I haven't come up with much. I used the guide posted on the following site to setup the NFS client on Windows 10:
https://graspingtech.com/mount-nfs-share-windows-10/
I get it all setup, but it never works. I always get a '53' error saying that the network path was not found. However it is correct. I have the same NFS share mounted in Ubuntu, and it works fine. It just doesn't work in Windows. I am not sure what would cause the issue.
Here is my NFS config:
server IP is 192.168.0.24
NFS Share Path is /mnt/Tower
The only option I have enabled is 'All Directories'
I have 'Mapall User' and 'Mapall Group' set to a specific user and group that exists on FreeNAS.
On the Windows machine I have installed the NFS client feature and the uid/gid setup in the registry for the user from FreeNAS for the Anonymous GID/UID setting. I have rebooted multiple times since setting that value.
The command I am using in Windows to map the drive is:
No matter what I do I get "Network Error - 53"
I have tried disabling my firewall on my Windows machine and I get the same error.
As I stated at the beginning, the exact same NFS share is able to be mounted from Ubuntu just fine, so I think it has to be something on Windows, but I am not sure what else to try.
Any assistance would be appreciated. Let me know if there is any info that you need to assist with coming up with a fix.
Thanks in advance!
https://graspingtech.com/mount-nfs-share-windows-10/
I get it all setup, but it never works. I always get a '53' error saying that the network path was not found. However it is correct. I have the same NFS share mounted in Ubuntu, and it works fine. It just doesn't work in Windows. I am not sure what would cause the issue.
Here is my NFS config:
server IP is 192.168.0.24
NFS Share Path is /mnt/Tower
The only option I have enabled is 'All Directories'
I have 'Mapall User' and 'Mapall Group' set to a specific user and group that exists on FreeNAS.
On the Windows machine I have installed the NFS client feature and the uid/gid setup in the registry for the user from FreeNAS for the Anonymous GID/UID setting. I have rebooted multiple times since setting that value.
The command I am using in Windows to map the drive is:
mount -o nolock anon \\192.168.0.24\mntT\Tower X:
No matter what I do I get "Network Error - 53"
I have tried disabling my firewall on my Windows machine and I get the same error.
As I stated at the beginning, the exact same NFS share is able to be mounted from Ubuntu just fine, so I think it has to be something on Windows, but I am not sure what else to try.
Any assistance would be appreciated. Let me know if there is any info that you need to assist with coming up with a fix.
Thanks in advance!