regression: Boxee not working with HaneWin NFS on version 1.5.0.23422

yoos added a comment - 08/Jan/12 2:42 PM Also, I am using the usb thumb drive I have used at least 10 other times successfully to load firmwares on my boxees. I even reloaded 1.22 on them using the same thumb drive and 1.22 works fine with nfs.

Mike Scattergood added a comment - 08/Jan/12 9:28 PM I am using the unregistered Hanewin v1.1.77 and it is working correctly for me. It does seem to take a long time for the shares to actually show up (the circle keeps spinning for a good minute to minute and a half), and then the IP is displayed for my PC server, not the machine name. I have my export list set up this way: d:\ -alldirs e:\ -alldirs f:\ -alldirs Once the server IP shows up in the source list, I can drill down and I have a list of the drives (d,e,f) and can drill down into them for the shares I have created in Windows.

Pete Smith added a comment - 08/Jan/12 10:47 PM Since installing version 1.5 I cannot connect to my Synology 211j using NFS...when I select "files", my server and then the folder I want (movies, TV shows, etc) it takes me back to the server selection menu without an error given. If I then select the NAS box again I end up in a "loop" trying to access the files...I had no problems with 1.22 and have not made any other changes to my network since before/after installing 1.5.

Jeff Wawryk added a comment - 09/Jan/12 5:08 AM - edited It's working for me, but very slow to resolve a share, takes up to 30 seconds after I click on it to see the contents. Was much quicker with1.2.2.20482.

Eric Millan added a comment - 09/Jan/12 5:11 AM I am also getting the same NFS errors that have been listed by Pete Smith. I am using a Netgear ReadyNAS Ultra 4 with the latest firmware. I also had no problem with Boxee version 1.22. I originally tried to upgrade my Boxee box firmware, then I performed a complete reset.

Eric Millan added a comment - 09/Jan/12 5:31 AM Debug log from my boxee box, when using a Netgear ReadyNAS Ultra4.

Kosta Bryman [Boxee] added a comment - 09/Jan/12 7:56 AM @Yoos - please attach your exports file for the NFS server. @Eric Millan - Please attach the full log package for this boxee.log Couldn't reproduce with HaneWinNfs 1.1.77/1.1.75 on windows 7, although there is a small delay in accessing files between the Boxee 1.2.2.20482 and 1.5.0.23422

Kosta Bryman [Boxee] added a comment - 09/Jan/12 10:07 AM @ Pete Smith - in the Synology admin interface, navigate to control panel -> network -> network interface and verify that the Jumbo Frame is disabled.

yoos added a comment - 09/Jan/12 11:33 AM I just uploaded my haneWIN settings screen shots too if that helps. Let me know if you want anything else

Kosta Bryman [Boxee] added a comment - 09/Jan/12 11:50 AM @yoos please check what is the status if the jumbo frames. right click on my computer -> manage -> device manager -> network adapters -> open the network adapter and the advanced tab, on the property windows locate jumbo frame and disable them.

yoos added a comment - 09/Jan/12 11:54 AM @ Kosta - I have 4 network adapters there. 1 "regular" one (Realtek PCIe GBE Family Controller), 1 virtual box and 2 VMware. The only one that has an advanced tab is the regular Realtek one and jumbo frame was already disabled.

yoos added a comment - 09/Jan/12 11:57 AM @ Kosta - FYI my 3 virtual ones were disabled too (I think because I uninstalled vmware and virtual box some time ago?)

Jeff Wawryk added a comment - 09/Jan/12 1:59 PM - edited @ yoos Please check Allow mount of remote devices and check UTF-8 Character set, Uncheck NFS Server Protocol Version 2 and change Maximum NFS Transfer Size (bytes) 32768 and Number of UDP NFS Server Threads to 32, In your exports file, you need to put in the IP address of the Boxee after the alldirs switch, then restart Hanewin. Eg. r:\ -alldirs IP_ADDRESS_OF_BOXEE If still doesn't work, Please make sure you have opened Ports 111, 1058, 2049 UDP and TCP in Windows Firewall (Inbound Rules).

Eric Millan added a comment - 09/Jan/12 2:14 PM - edited @ Kosta: Here is my full log package from my Boxee box.

yoos added a comment - 09/Jan/12 2:16 PM @ Jeff - OK I'll make the changes and test later tonight when I am home, thanks!

yoos added a comment - 09/Jan/12 7:23 PM - edited @Jeff - I tried all the nfs settings, shut down and restarted HaneWin and the boxee but it still doesn't work. I don't understand why I'd have to enter those IP addresses as my boxees work fine on 1.22 using nfs the way I had it set up. I tried what you suggested anyways... Since I have multiple boxees would I do the following? r:\ -alldirs 192.168.1.102 p:\ -alldirs 192.168.1.102 r:\ -alldirs 192.168.1.103 p:\ -alldirs 192.168.1.103 The only thing I didn't try that you suggested was ports. I don't get why that would be an issue since boxee 1.22 works fine with nfs. Furthermore, if I click Files > NFS > PC_Name and either click PC_Name 3 more times or 2 times and try to back out, boxee pauses for a moment and "reloads" to the initial large splash picture and then the home screen appears. This just does not sound like an NFS error to me, but a boxee problem imo. I went back and forth between 1.5 and 1.22 on both my boxees several times this weekend and 1.22 worked fine every time with nfs and 1.5 did not.

Jeff Wawryk added a comment - 09/Jan/12 7:54 PM - edited r:\ -alldirs 192.168.1.102 192.168.1.103 p:\ -alldirs 192.168.1.102 192.168.1.103 I would definitely try opening the ports in Widows Firewall and possibly your router. Would also like to know if you have any other software firewalls and what AV if any are you using?

yoos added a comment - 09/Jan/12 8:22 PM Why does it have to be so complicated when I can put boxee firmware 1.22 on this box and nfs will work perfectly? Why would 1.5 now cause all types of port or AV issues?

yoos added a comment - 09/Jan/12 8:29 PM - edited So this is what I just tried... Settings > File Sources > add sources > NFS > Manually Enter IP/Name > (box pops up) > Enter IP of PC where vids are (no user/pwd) > I see my folders immediately and can add a source. So if I put an IP in for nfs it works, it isn't working when I select my pc name (which shows up as mike-PC.local if that matters) There's no way to browse files with nfs/IP though...

Jeff Wawryk added a comment - 09/Jan/12 8:36 PM I would suggest setting a static IP for the computer that hanewin is on.

yoos added a comment - 09/Jan/12 8:40 PM - edited so I added my sources with the IP using nfs, deleted my smb sources, and clicked advanced > clear media to do a rescan. We'll see what happens. This is the same issue I had in smb with 1.2 (pc name wouldn't work, only IP), which was one of the reasons I went to nfs (another because nfs is faster). I hope this original issue I posted gets fixed!

yoos added a comment - 09/Jan/12 8:41 PM @Jeff - I have a static IP on it, ty!

yoos added a comment - 09/Jan/12 8:43 PM I also changed my hanewin exports back to the following for simplicity... r:\ -alldirs p:\ -alldirs I retained the other settings you recommended in hanewin and will test after the scan is done to see if that speeds things even more.

yoos added a comment - 09/Jan/12 8:45 PM it is now time to enjoy some Indian curry.

Pete Smith added a comment - 10/Jan/12 12:00 PM @Kosta: Jumbo frame has been disabled from the beginning and after checking now still is disabled...is that the setting it should be?

yoos added a comment - 10/Jan/12 7:53 PM @Jeff - omg, with those hanewin settings you told me to change it allowed me to increase the mbps throughput! My one boxee went from a max 70 mbps birds test file to 100 now and the other from 45 to 70! That's awesome! Thx!

Kosta Bryman [Boxee] added a comment - 11/Jan/12 7:32 AM @yoos, the drives r:\ and p:\ are network drives that you mapped to the machine where the NFS server is installing?

yoos added a comment - 11/Jan/12 8:24 AM - edited @Kosta, they are both drives "mapped" to my Vista desktop. I don't know if mapped is the correct terminology, but here are more details. I have a Vista PC. Drive R is my RAID Sans Digital unit (TR5UT+B, connected with eSata), which Windows recognizes with no problems. I can actually see this drive connect in BIOS as it boots up also, but I'm not sure if it gets re-recognized in Windows as R when Windows logs in. Drive P I "map" after I log into windows with Truecrypt. I have an encrypted "container file" on the RAID drive, which I connect with Truecrypt and Windows sees it as drive P when I connect it, since I choose P as the letter in Truecrypt to connect to. Windows doesn't recognize this drive until I connect it in Truecrypt, which I usually do right after I log into Windows. Both R and P are on the same machine where HaneWin is installed. On a side note, NFS is better/easier than SMB when it comes to Truecrypt because with SMB I'd have to re-setup the permissions of the P drive after I connect it in Truecrypt after each Windows login, whereas with NFS I don't have to do that. With NFS I simply connect the file/drive in Truecrypt and it's instantly available with no extra steps necessary.

yoos added a comment - 11/Jan/12 8:39 AM Just a comment here to notify you I edited my response above and added more info, in case you read the original response.

Rafael Mizrahi [Boxee] added a comment - 11/Jan/12 8:45 AM yoos, I see in your log that the Source is defined to nfs://mike-PC.local please do not add sources to root of servers. try to remove the source and create a new one which points to a folder inside nfs://mike-PC.local

yoos added a comment - 11/Jan/12 9:43 AM - edited @ Rafael - I don't understand... On my PC I have nfs setup with the following: r:\ -alldirs p:\ -alldirs If I understand what you're asking, you are saying in BOXEE to setup a source that is on a folder in drive R or P instead of setting up a source for the root of R or P. In fact what I was trying to do was exactly what you are suggesting (If I'm understanding correctly). In each drive I have a folder called Media, and in that one called DVD for example, so I want to setup my BOXEE source as basically R:\media\dvd. The problem is I can't even see the media folder to dig deeper to dvd on boxee. I just see the pc name mike-PC.local when I go to add the nfs source and when I click on it nothing happens, it doesn't show my media folder for me to add the source. If I try to click my pc name a few times boxee diverts back to the large logon logo and then the home screen appears. I'm not trying to add the root drive as a source in Boxee.

yoos added a comment - 11/Jan/12 9:44 AM As I mentioned before, this all works fine in boxee 1.22. I can go to add sources, click on nfs, click on my pc name, dig into the media/dvd folder and add it as a source.

Jeff Wawryk added a comment - 11/Jan/12 1:20 PM - edited @ yoos example: r:\media\dvd -name:dvd 192.168.1.102 192.168.1.103

yoos added a comment - 11/Jan/12 2:37 PM - edited OK I entered the following ONLY in hanewin exports and restarted the nfs server: r:\Media\ -name:Media 192.168.1.102 192.168.1.103 This change in hanewin didn't help... If I go to Settings > File Sources > add sources > NFS > I see my pc name again (mike-PC.local). When I click on my pc name the circle just spins and spins, the same issue as before.... If I instead choose the option "Manually Enter IP/Name" (no user/pwd) > I immediately see /Media now, and it works again as with my original settings below using the IP option: r:\ -alldirs p:\ -alldirs This has to be a boxee issue imo... not a hanewin or pc issue... I'm doing everything the same with the same setup and the only difference is boxee version 1.22 vs 1.5 where 1.22 works with nfs fine and 1.5 doesn't.

Mike Scattergood added a comment - 11/Jan/12 3:17 PM What's funny is I never see the PC name in the NFS sources, only the IP of my PC server. The issue must be in the way Boxee is discovering the identity of devices acting as NFS servers. Since my Boxee always saw my source as an IP, it didn't break when I updated to the newest firmware. Interesting...

Jeff Wawryk added a comment - 11/Jan/12 3:24 PM Same here, I just see the IP, not Computer name and NFS is working fine for me.

Eric Millan added a comment - 12/Jan/12 12:00 AM Do you need anything else from me, or have anything else for me to try? Remember, I'm not using the hanewin software, I'm using a netgear nas. 1.2 worked perfectly, 1.5 does not. I did check on my own system based on some feedback given here, I have jumbo frames disabled on my nas. I can try anything you would like.

Kosta Bryman [Boxee] added a comment - 12/Jan/12 7:56 AM Eric and Pete, please remove the source and add again via the IP address as Yoos described - open the settings -> file Sources -> add source -> nfs -> manually enter ip/ name Please preform it in debug mode and upload the log, thanks.

Eric Millan added a comment - 12/Jan/12 5:43 PM - edited I removed all shares, and re-added them via the IP address of my NAS using NFS. I uploaded my logs, the file is boxee.1326407884.2675.tar.bz2. I tested it after it scanned my directory, everything was working.

yoos added a comment - 17/Jan/12 10:20 AM FYI, this issue still exists in Firmware 1.5.0.23556

Eric Millan added a comment - 18/Jan/12 2:29 AM I also updated to the latest version, and the NFS issue still happens for me as well in 1.5.23556.

yoos added a comment - 20/Jan/12 6:24 PM FYI, this issue still exists in Firmware 1.5.0.23615(20th January)

Paul Rodriguez added a comment - 08/Mar/12 8:27 AM - edited I am using haneWIN 1.1.77 on a Win 7 machine. I can add my shares and play them back just fine. The scanning process, however, takes forever and is incomplete. I've left my box on for days and it has yet to fully identify all my files on NFS that only takes a single evening to identify on SMB.

Will added a comment - 05/Apr/12 1:11 AM Indeed NFS is totally broken with firmware 1.5. :( I have gone back to Firmware 1.2.2.20482 and working fine once again. Please fix this ASAP.

Jeff Ryan added a comment - 16/Jul/12 3:05 PM When is this going to be fixed, BOXEE???