I am sorry to resurrect this thread, but it still seems to be relevant. Same issue: I can access my NFS share from within Kodi as long as I know IP and path, but discovering is not possible.
When selecting "Network File System (NFS)" as the type of media share, i just see a spinning circle for a few seconds and that's it. This is the debug log:
Quote:16:54:40.921 T:139948518770432 DEBUG: SECTION:LoadDLL(libnfs.so.12)
16:54:40.921 T:139948518770432 DEBUG: Loading: libnfs.so.12
16:54:41.421 T:139949381940736 DEBUG: ------ Window Init (DialogBusy.xml) ------
16:54:43.953 T:139949381940736 ERROR: GetDirectory - Error getting nfs://
16:54:43.953 T:139949381940736 ERROR: CGUIDialogFileBrowser::GetDirectory(nfs://) failed
16:54:43.953 T:139949381940736 DEBUG: Keyboard: scancode: 0x24, sym: 0x000d, unicode: 0x0000, modifier: 0x0
16:54:44.204 T:139949381940736 DEBUG: ------ Window Deinit (DialogBusy.xml) ------
I am very curious what mechanism Kodi is using to discover NFS shares. To the very best of my knowledge there is no magic discovery mechanism for the NFS protocol. The next best thing would be Zeroconf (Avahi), but announcing my NFS share via Avahi does not help when selecting "Network File System (NFS)" inside Kodi (but I can see the share when selecting "Zeroconf browser", as expected).
By the way, the NFS server is an Arch Linux machine. The configuration seems to be correct, as Kodi can access the share just fine when manually providing IP and path.
Does someone know how this NFS discovery of Kodi is expected to work theoretically?