Firefly incompatible with iTunes 10.5

mdgm wrote:
Did you install one of the earlier versions of the update? If so, that would explain why you have problems. The current version of the add-on is 1.0.3. I have a suggestion here: http://www.readynas.com/forum/viewtopic.php?p=328221#p328221 or here: http://www.readynas.com/forum/viewtopic.php?f=22&t=58468&p=328951#p328951

Thanks mdgm,

I just ordered an extra 2tb drive, going to do a backup, update and factory default when it arrives. I will wait until then to clean things up, this will give me a few days to tidy up the music meta data anyway.

How do I access the system folders to manually configure?

What do you want to manually configure?

You'll need to install the Firefly update addon after doing the factory default.

I've updated the server to 1.0.3 but I can't find the application on the Streaming or Install-Add on tabs. Logs show that it's been installed. I've even rebooted and tried again and still it's not showing up. Running firmware 4.1.8. Anyone have any suggestions?

Clear web browser cache

If still not visible do OS re-install then install add-on again

Reinstalled 4.1.8 and then the iTunes Server 1.0.3 again and it's taken it this time. Problem is that I'm seeing the server in iTunes for a few minutes and then it just disappears. Even close/reopen iTunes doesn't make it show up again. Running 10.5.0.142.

Connected via ethernet or wireless?

Sounds like your current issue could be a Bonjour related issue.

There are numerous reports of Bonjour problems unde 4.1.8 which have yet to be addressed by Netgear.

Accessing systems via IP address can workaround this in some scenarios a, but unfortunately not with iTunes. Probably not much can be done at this time except to try to stop and restart the Bonjour service in Frontview

Connected via wireless from the laptop running iTunes, NAS is into the Gigabit wireless switch. Problem is still happening, soon as you link on the server in iTunes it just disappears.

There is now a 4.1.9 beta release. Though there is no specific information regarding this issue being addressed in the beta, it might be worth a try

Upgraded to 4.1.9-T2 and problem remains the same.