AFP access stopped working in new locale

[RoyalEF]

Boxee Box (latest firmware)
Netgear NDR3700v2 Gig Router
NetGear ReadyNAS
MacBook Pro OSX 10.6
- everything wired

Everything's been working for months. I relocated my setup to an RV using a 2nd router (same model)
Boxee won't access the the Media shares (fully scanned & ID'd via AFP). It knows the host as NAS (NAS.local internal reference). I can access then by Browse via SMB & UPnP.

Media share is read-only accessible to Guests via AFP in Mac OSX. Also a username/pass will access as read/write.

Everything can talk to everything. Mac has no AFP issues with NAS.

But Boxee can find any files. I turned up syslog to default (sending them to the IP address of the NAS--my syslog server). The only relevant message is :

May 14 18:32:54 192.168.1.7 boxee MountShare - Failed to mount [/tmp/mnt/afp_NAS.local_media]

I can't figure out what the issue is. Even if I use the privileged user/pass(r/w) with the boxee it just keeps says "LOADING ERROR - Could not access file, directory or device"

The only thing I can think of is that it is failing to find the NAS via a network scan and therefore can't resolve the NAS name to it's IP address. But I don't know how exactly AFP handles names or how Boxee finds an AFP name. At home I would have a FIOS router also, so I don't know if it was offering up a AFP-compatible Name Resolution. I used this setup in the RV last year. I didn't have issues--although I wonder if I used IP addresses instead of names. I don't think I did, but ...

Any ideas?

[RoyalEF]

Don't understand the why...

but "NAS.local" is no longer valid. I never understood why Boxee called it "NAS.local" in the first place because it is just "NAS", but it has been that way for months.

I went to add a new share and chose IP/name... despite "NAS (AFP)" being listed as found--but not working.
I entered "NAS" and blank user/pass and it worked.
So I could add a copy of the share with the "NAS" definition. Now, of course, I have to remove all the built shares, add them, then spend many hours still SCANNING them... but I don't have a good internet connection here. And despite all the NFO and TBN and such, it seems to refuse to scan/ID without an internet connection. So my mobile hotspot is now on and Boxee is chewing through my paid bandwidth just to re-discover, yet again, the NFO & TBN files.

Coverting to NFO/TBN/local thumbs is a lot of work and even afterwards it is you still have problems because of other funkies. I wonder if I will ever be able to have an offline boxee with nice thumbs and NFO.

[RoyalEF]

MOved the whole setup router,NAS, Boxee back home to make use of Internet. Removed all 7000 items from boxee. Re-added over two days times. Everything looked good. Picked the whole setup up and moved it into the RV.

None of the files can be found via AFP. NAS (AFP) is listed as found, but when I select it NAS.local appears under AFP://, and it lists NAS(AFP) again. Continuing just prompts for a password and no matter what, it can't find it.

SMB & UPnP work on boxee. All the other devices in the house access the same NAS files with AFP & SMB. Only boxee is broken, only on AFP.

Despite the fact that it scanned 7,000 items and ID'd them via AFP.

I'm so spent trying to get this box setup to work with a large library. I don't have time to mess with it, yet again, before hitting the road, and my internet will be limited for the next three months. I will have to live with it broken and browse for all movies and tv-shows via BROWSE & SMB. Boxee has seemed reluctant to scan when it didn't have an internet connection and I don't want my mobile hotspot paid bandwdith eaten up wastefully scanning and communicating with boxee.tv when I have 7,000 NFO and TBN files on the share.

sigh.

Hopefully the next firmware will make this box work. This is NOT a consumer product.

[darcilicious]

If you want to make sure the devs are aware of this issue you'll need to report this issue here: http://jira.boxee.tv -- also you'll probably be asked to turn on debugging and attach the logs.