2016-01-21, 15:37
(2016-01-21, 04:22)mbriody Wrote: Thanks, will try adding the IP for NFS. You mention adding this under Zeroconf. Any reason to do it there rather than under NFS? Or does it not matter?
The Browse menu "Network File System (NFS)" button doesn't work here for me period just as the "Windows Network (SMB)" one doesn't either (It does works if I have a Windows based share available). When ZeroConf is working right, it will bring them up correctly on an OS X server. But if you manually add a share so it has your SMB or NFS address, it will then show up on that Browse screen with the manual address starting point and you can then use that to add any number of sub-directories, etc.
Why OS X doesn't show up under the regular Windows Network or Network File System listings, I do not know. It never has for me under any version of OS X (even with SMBuP). Manually entering a SMB address (e.g. if I had a drive called "MedaFiles" I set to share and I was at 192.168.1.4 you would want smb://192.168.1.4:445/MediaFiles/ as your entry point (you can then get at all directories below that; you'd have to put something else for a share on another volume; just match whatever you set up in your OS X preference menu shared drives and/or directories (smb://192.168.1.4:445/NAME works for any given listing). Just going to Windows Network (SMB)" in the Browse list doesn't work for OS X (not for me anyway). It will say something like "Error 2: Share Not Available" if you try to use the Windows Network button. It doesn't say anything if I click on the Network File System button (busy and then nothing). Maybe there's a way to fix that, but I don't know what it is.
Similarly, to get to my main NFS share with that setup if I had it shared the same way, I would set a link to NFS://192.168.1.4:2049/Volumes/MediaFiles/ as the entry point (again assuming MediaFiles is an actual drive and you had it set up that way when you set up NFS on OS X in general).