I've followed the guide to getting NFS to work on my MBWE bluerings. I'm on firmware 18.104.22.168 so I had to download nfs.zip and restore the binaries. Everything is working well except that I cannot connect using the Windows NFS client. I'm using Windows 7 Ultimate, so it's built-in.
For whatever reason, I cannot mount any NFS shares from my MBWE. I can do a:
showmount -e ip_of_mbwe
and it'll list all export shares, but everytime I try to mount, it'll come back with an error 53, which is that the network path isn't found.
The commands I'm using are:
mount ipaddress_of_mbwe:/share/directory X:
I am definetely sure that NFS is running correctly since I can access and mount the NFS shares using a raspberry Pi (running openelec). Also I have a virtual machine running Slackware 13.1, which when running via this Windows 7 machine can also mount and access the shares via NFS. Strangely enough I can mount and access NFS shares from the virtual machine using the NFS client on windows.
While I'm also running samba, I have ensured that Win 7 prioritizes NFS over samba shares. Also, I've put in the relevant guid's and uid's in the registry.
I have followed just about every single guide and google'd everything and I can only presume that the windows 7 NFS client has some kind of problem? Fortunately, I stumbled across some kind of hacked workaround (from a forum where people discuss accessing Popcorn Hour media units):
This actually works but with the drawback that it doesn't survive a reboot. I have no idea why it works either.
I can only conclude that either there is some kind of problem with the NFS client for Windows or maybe the NFS binaries need updating for provide a newer version for our MBWE's?
If anyone can assist, it'd be most appreciated. Thanks.