FreeNAS NFS not discovered by machines on the network

[fjalvingh]

I just set up a FreeNAS server and want to connect to it using NFS. For most other NFS servers, just using your Linux file explorer of choice would show the NFS servers available on the local network so that you can mount their resources. The same goes for things like KODI. But this does not work for FreeNAS.

The problem seems to be caused by mountd in freenas: this registers the protocol version 1 and 3 for 100005 (mountd) while apparently the convention is to scan for version 2 to discover nfs servers. So executing

rpcinfo -b 100005 2

does not find the FreeNAS server while

rpcinfo -b 100005 3

does.

Making the NFS mounts browseable is no much nicer than forcing people to connect by entering IP addresses.... Does anyone have an idea how I can get FreeNAS NFS discoverable, or how I can force the mountd version on freenas to register version 2 too?

Thanks,

Frits

 

[Ericloewe]

Maybe this would be a good feature request.

 

[Milhouse]

This post may be relevant: https://forum.kodi.tv/showthread.php?tid=346920&pid=2882589#pid2882589

I'm still on FreeNAS 8.3 and it's broken with respect to Kodi, as is UnRaid.

Does rpcbind in FreeNAS 8+ enable remote calls? If not, can --enable-rmtcalls be enabled?