Anyone out there using a NFS server for Windows?

[browellm]

I just used this guide to install and configure NFS for my WHSv1, which is just Windows Server 2003 really.

http://www.mediasmartserver.net/2009...up-nfs-in-whs/


Works well.

[aaronwt]

I just used this guide to install and configure NFS for my WHSv1, which is just Windows Server 2003 really.

http://www.mediasmartserver.net/2009...up-nfs-in-whs/


Works well.

So does using NFS make any difference with the new beta release? Does it solve the audio dropout problem? IF it does I will consider using it on my WHS. And there is an option to use NFS with my unRAID as well. I think even my INtel NAS has an option for NFS.

[browellm]

So does using NFS make any difference with the new beta release? Does it solve the audio dropout problem? IF it does I will consider using it on my WHS. And there is an option to use NFS with my unRAID as well. I think even my INtel NAS has an option for NFS.

I haven't installed the latest betas, but I will do and report back for you.

[drunkwithpower]

The only one I know of is http://www.hanewin.net/nfs-e.htm which some folks seem to be using successfully. There was a Boxee bug recently closed related to this software with the comment something to the effect, "NFS works with properly configured servers" apparently indicating that if the above software is configured correctly, Boxee will use it just fine.

I haven't used it personally myself. (SMB or DIE! )

Do you stream blurays via SMB? I have tried this but the buffering is terrible. I have powerline adapters and am getting about 275mb/s bandwidth. According to everyone this exceeds anything bluray can throw at it. But my Boxee still buffers every 30 seconds. Then, after I back-rev to firmware v1.1.3.19252, my blurays stream pretty darn well. I even have excellent success streaming them wirelessly (via N router - ASUS Black Diamond router). This seems to indicate to me that the problem lies somehwee within the firmware. Is it SMB? I don't know. Does anyone know why this would happen? The only reason I went to an earlier firmware was because someone said it would work, and it does.

Also, I think the answer from the dev team is the reason they get so much hate. All they have to do is setup a test in their dev environment, confirm it works, and then have someone create a short writeup to show the configuration. If they did this, everyone with problems would at least be able to compare what they did and figure out how they might proceed. And if they setup everything the same way as the dev tea and it still doesn't work, one would surmise there are other issues at play that need to be addressed. I think most people think that because they didn't perform the write-up, they really didn't test it and are just closing it because some people mentioned theirs works.

I have been extremely positive so far, but I find myself leaning toward the pessimistic after reading the dev team's explanation for closing.

[goge]

I just bought a Boxee Box and imidiately ran into problems with SMB and BD ISO files.
I'm using a HP MediaSmart server with WHS (2003 based).

I installed Hanewin NFS for my films, and now it runs like a dream. But installing Hanewin NFS wasn't Plug and Play. From different articles I put this together:

Download Hanewin NFS software from this site: http://www.hanewin.net/nfs-e.htm

Connect to your WHS server via RDP (mstsc.exe) and log on as administrator.

Goto to Control Panel and Windows Firewall.

Add the following 6 exceptions to make sure that Hanewin NFS is not blocked
Hanewin NFS TCP 1058
Hanewin NFS TCP 111
Hanewin NFS TCP 2049
Hanewin NFS UDP 1058
Hanewin NFS UDP 111
Hanewin NFS UDP 2049

Restart Windows Firewall (Or in the end of all this, restart your WHS box)

Now scroll back up and click on your Hanewin server that is listed on the control panel as well. Once you click on this it will bring up another window with the tabs NFS/Server/Exports/Mounts/Portmapper/Language Click on the NFS tab first.
Make sure everything is checked except:
NFS server Protocol version 2.
Make sure the numbers shown from top to bottom are:
1058/2049/4/32768

Now click on the Server tab. Make sure that you check:
ALLOW MOUNT OF REMOTE DEVICES

Now click on the exports tab. Click edit export file and type in the location of your movies on your WHS.
example D:\shares\Videos\Movies -readonly -public -name:Movies
Now click on:
restart server.

If you did not restart your Windows Firewall on WHS server earlier, then do so now.

After restart, you should be able to see the NFS share on Boxee.

I have "stolen" a lot of information in the article that this link goes to: http://wiki.wdlxtv.com/Windows_Home_...Win_NFS_How_To

Thos does not free the Boxee people from the oblligation to correct the SMB problem. Hanewin NFS is cheap but not free. But thanks to Hanewin for putting out a 30 day free trial.

[dladrach]

If you can get Boxee to actually admit that they have an SMB issue (they may be admitting it at this point). I fought the SMB issue when I first bought the device when they first came out. Always getting "it is your network not Boxee". Funny thing, I switched to NFS as soon as it was supported and all buffering problems went away.

[dladrach]

Just so folks have it, here is my Exports File.

f:\blu-ray -readonly -range 192.168.1.1 192.168.1.255
f:\movies2 -readonly -range 192.168.1.1 192.168.1.255
f:\shows -readonly -range 192.168.1.1 192.168.1.255
g:\movies -readonly -range 192.168.1.1 192.168.1.255

I know it was stated earlier it works when configured properly. I am the one that opened that ticket and Boxee's response is not 100% accurate. The scanning issue remains regardless if you put the f:\-alldirs g:\-alldirs in there.

[drunkwithpower]

Just so folks have it, here is my Exports File.

f:\blu-ray -readonly -range 192.168.1.1 192.168.1.255
f:\movies2 -readonly -range 192.168.1.1 192.168.1.255
f:\shows -readonly -range 192.168.1.1 192.168.1.255
g:\movies -readonly -range 192.168.1.1 192.168.1.255

I know it was stated earlier it works when configured properly. I am the one that opened that ticket and Boxee's response is not 100% accurate. The scanning issue remains regardless if you put the f:\-alldirs g:\-alldirs in there.

I've found that the problem is the same as with SMB - if you turn Boxee off completely then sporadically it loses the ability to connect to SMB/NFS sources after boot. I have to reboot my server to get it to see everything again. This may not happen to everyone, but this is my experience.

[aaronwt]

...............
Thos does not free the Boxee people from the oblligation to correct the SMB problem. Hanewin NFS is cheap but not free. But thanks to Hanewin for putting out a 30 day free trial.

With the current firmware I've only run into one BD ISO with a problem over SMB, Gran Torino. And it's not even a high bitrate BD ISO. My high Bitrate BD ISOs have streamed fine with SMB using my WHSv1 and my unRAID.

When I tried Gran Torino using NFS it was fine. No idea what the issue was.