I think it is the Firmware 7.4.2 on the Airport Express. I just downloaded it and it immediately broke - I cannot connect to the AE anymore. What rubbish. I'm going to try to downgrade back to 7.4.1
Hi - Problem this morning (12Jul09) with Airtunes and remote speakers.
My specs: MacBook Pro 2.4gHz/iTunes 8.2(23)/new Airport Express 11n firmware 7.4.2 on a Time Capsule network.
When first set up Airtunes worked fine. Music went to household music system as it should. Speakers as shown in iTunes were selectable and still are. All Airport units glow green and all are accessible. All appropriate boxes are checked in iTunes prefs and Airport Utility. No new software or updates have been added.
When I stream music to the remote speakers I get the -15000 error message. Restarts, app quits and device restarts have not fixed the problem. Apple's support item on this error is both out of date and inapplicable to me given I have the latest firmware installed for Airport Express 11n.
Me again. I dropped back to firmware update 7.4.1 and all works well. Airtunes functions as it supposed to do. If anyone else experiences the problem described in my earlier post today, try reverting to 7.4.1. Apple will catch up with the problem eventually.
By the way, the Remote app on my iPod Touch works beautifully for controlling music play on "Computer" and other speakers alike. My Bose iPod unit is almost useless now given that I can easily control music on the main system from anywhere on the property. (Yeah, I still use the Bose to recharge the Pods.)
Glitches or not, Apple is still great. I love the Windows whinging from family holdouts... 87 down, 2 to go. Resistance is futile. 🙂
I set up the Express in Create a network mode instead of Join network mode. It doesn't have an internet connection now but I only need this for streaming music. So I now use the Airport on my iMac only to connect to the Airport Express music network. For the internet I have the ethernet cable. This solved the issue of being unable to reliably connect to the Express when it was in Join network mode.
+I set up the Express in Create a network mode instead of Join network mode. It doesn't have an internet connection now but I only need this for streaming music. So I now use the Airport on my iMac only to connect to the Airport Express music network. For the internet I have the ethernet cable. This solved the issue of being unable to reliably connect to the Express when it was in Join network mode.+
Not the most ideal situation do... you would like to have all wifi.. at least that is what I want... that is part why I bought the product... wireless stream my audio and surf the web...... and it should be possible... However I have had so many problems with this product. The time I spend on trying to solve the problem I could have done so many coding 😟
I previous got the -15006 error and my airtunes speakers disappear from time to time. Now i solve the problem by HARD RESET all the AirPort gears including AirPort Extreme Base Station and both AirPort Express (g). Don't be lazy, u have to reset EVERY gears from ground up or the problem persist. No more bothering about which firmware to use, firewall setting, check and rechecking airtunes option etc.
Hope it helps!
dinnymac - you've saved my night. 3 hours and several other fixes and nothing happened. Needless to say yours was the winning answer for me! Thanks and Cheers!
have the same problem, indeed, with Windows XP.
I can hear approx. 30 min. of music about the stereo with Itunes, then the connection breaks off. As a rule without error message. If I try the distant loudspeakers to activate anew, I also receive the error message-15000 or-15006.
The airport express is connected, in the meantime, by LAN in the same Router like the PC because I thought that the problem deals with the WLAN. Because WLAN is not active, however, now any more, it must lie somewhere else. Many tips on the Internet (Firewall deactivate, settings IPv6 change), everybody has not helped.
If the connection is away, I still come about the utility program near the device. Indeed, not about the automatic recognition, but above the way "other configuring" and then the IP address give (the device has a firm IP).
If I click then above the way on "updating" and cause with it a new start or separate the device briefly from the stream, it goes again for a while.
It is used iTunes 8.2.1.
I do not understand that the device should hang itself so...
Well, wanted to make known sometimes my experiences. Maybe somebody has any helpp for me. However, maybe it is also interesting for you that the problem is not only with MACs.
Edit: one more addition: apparently the thing also hangs itself if iTunes does not run at all
Skihase's solution posted last year worked for us!
I simply added a UDP port 6002 entry to our allowed firewall openings on our iMac G5 (OS 10.4.11, iTunes 8). That immediately took care of our "firewall preventing ..." and error -15000 problems when trying to play over AirTunes. Thanks!
Our situation was: AirTunes worked fine on our new (2009) MacMini running Leopard and on our WinXP machine, but our old iMac G5 running Tiger gave us the firewall error message when trying to play to the AirTunes speakers. Also possibly relevant was that only that iMac depended solely on WiFi for its Internet connection (the other computers are hardwired to the Internet).
Well maybe many of these fixes work for Mac OS other than Snow Leopard.
So far I have tried every one of the suggestions, rebooted devices, and still nothing.
Everything works fine when I use a computer running Leopard; this also proves that I didn't break anything along the way. Same version of iTunes on both and so on.
I think this needs to be resolve by Apple unless there is some setting in Snow Leopard I am missing.
I did change the firewall settings and turned those on and off and added iTunes as an application which allows incoming connections when it was on. That did not resolve it either.
I even reinstalled iTunes figuring maybe some of the system components got lost during the Snow Leopard upgrade but still no go.
Apple, please fix this.
