Previous 1 2 3 Next 38 Replies Latest reply: Feb 3, 2012 2:40 PM by alkerhj
Fookes Level 1 (20 points)



Just about to purchase Lion but still running Snow Leopard.  Upgraded iTunes yesterday though to 10.4.


Problem is this.  I've got my 1st Gen Apple TV (connected to surround sound) and an Airport Express (connected to speakers) in another room hooked up via Airplay - or at least I did have!


Now, when I attempt to 'tick' to add these two speakers to the Airplay icon in iTunes it blinks (milli-seconds) as though it's trying to add but then doesn't on either ATV or AE.  These worked beautifully before I updated iTunes.  Is this a known issue?  Would it be rectified (knowing the 10.4 update is geared towards Lion) once I have updated to Lion?


It's a pain in the rear so if anyone can help I'd appreciate.  I've not really seen same on here so I guess it's just me?!?

iMac, Mac OS X (10.6.8)
  • heiseheise Level 1 (0 points)

    I can confirm I also have this issue. I have a Pioneer VSX-1021K that I bought just for usage with Airplay (well, that and DLNA) that immediately stopped working with Airplay after the update to 10.4 last night. And it must be multiplatform, as well, because I run Windows 7 on a Dell.


    With me the timing is different though - I can 'connect' to the Pioneer and set it as the playback device; the time-out occurs when I actually press play in iTunes, then it gives me a -15000 error.

  • Nicholas Hardy Level 1 (5 points)

    Airplay does not work for me with a 802.11g Airport Express, it does work with a 802.11n Airport Express but it takes a long time for it to connect and stream.  The resonsiveness is very poor in comparison to iTunes prior to the 10.4 update.  Machine: MacBook Pro 15 i7 running 10.6.8.

  • bartfromhaarlem Level 1 (0 points)

    Airplay does not work with an airport express 802.11n after updating to lion and itunes 10.4. I've tried after connecting to a g network and to an n (5Ghz) network, to no avail.

  • Speedyben Level 1 (0 points)

    I have the same issue. All working well until upgraded iTunes yesterday and now get the error 15000 message when iTunes tries to connect to airport express.

  • bartfromhaarlem Level 1 (0 points)

    Reverted back to 10.3.1 (dont forget to get the backupped .itl file from the 'Previous iTunes Libraries' folder, rename it to 'iTunes Library.itl' and replace the file in the iTunes folder.


    I did have to change the firewall prefs to allow for incoming connections - dont know why it changed - maybe the install of 10.4 changed it or the lion install.


    After that, it worked fine again.

  • rprice54 Level 1 (0 points)

    Me three. Can't connect to my airport express (n) or second gen ATV. Bummer. Can I revert to 10.3 via my time capsule?

  • timothy sfromarvada Level 1 (0 points)

    Had the same frustrating issue...  I have (3) Airport Express' and (1) 1st Gen Apple TV.  All was working fantastic until I installed 10.4.  I would select which speaker I wanted and it would display "Connecting to Airplay" (which I had never seen before) - and would think and think and then the dreaded unknown error code -15000 kept popping up.  Then I decided to try and push content via iTouch and iPad and both worked without flaw.  So I decided to reinstall 10.4 again with the same results.  After that, I began suspecting a network issue. 


    I then went into my advanced settings within my Windows (Vista) Security Center - iTunes was selected, and still the same -15000 error code.  After being in my Security Center, and noticed that iTunes Help did not have the the procedure correct, I began looking around and discovered a little note on my Vista Security Center that stated having 2 firewalls can cause some some networking conflicts (I currently have McAfee protection), which also has Firewall protection.  So, after reading that friendly note on the Security Center, I turned off my Windows Firewall, which doing so still noted that I my Firewall was on -- but only via McAfee.  Once I did that - viola - all speakers, including Apple TV connected immediately. 

  • heiseheise Level 1 (0 points)

    Heh, I should have known to try a firewall fix first. Disabling the Windows Firewall fixed the connection issue for me too, but of course this is only a temporary fix because I'm not going to run my computer without a Firewall just because iTunes seems to require it now.


    I can see from the preferences that iTunes should have already poked holes into the Firewall for its own purposes, but they're not working anymore since 10.4.


    I'll email Apple directly about this, now that we have a specific fix. Thanks!

  • rprice54 Level 1 (0 points)

    I'm on a Mac. I reset my firewall settings with no luck :/

  • heiseheise Level 1 (0 points)

    Well, I don't claim to know much about OSX, but Windows gives us the ability to monitor and change both incoming and outgoing firewall rules. It's possible that OSX (in Apple's infinite wisdom) only gives you access to incoming firewall settings (and reset abilities) because that's more likely to be where attacks come from.


    I notice you say you "reset" your firewall settings. Try disabling the OSX firewall completely, and see if you can connect - don't just reset, because that will restart the firewall, and the whole point of testing this hypothesis is to see if airplay works without the firewall turned on.

  • rprice54 Level 1 (0 points)

    Good point about the firewall.


    I had been having some other issues after the Lion upgrade and had not done the one thing I used to do all the time when I was using Windows. Shut the thing down- all the way, just not a restart. Fixed all my problems including this one. Who knows. I've just gotten so used to leaving the mac on all the time, and usually a quick logout is all I need if problems arise, I skipped a basic step. All seems to be well now.

  • timothy sfromarvada Level 1 (0 points)

    I noticed you were using PC also...  Do you have additional virus protection?  As noted in my previous reply, I had to turn one or the other off since Windows noted that having 2 Firewalls (Windows & McAfee) on at the same time caused network conflicts.  When turning off the Windows Firewall, it still showed I had a Firewall active in which McAfee took over. 


    I should also add for the post that in the past, since I got to the 10.1 version of iTunes, I immediately began to experience audio drop outs - which of course will drive you crazy.  Since the little Firewall exercise today, I have not had one drop out - even out in my garage (detached) and appears to be running as good as the day I installed them.  So the question is; is it a coincidence, or was that the drop out issue all along since the 10.1 version came along? 


    Also keep in mind that I have had these settings on my Firewall all along and wonder if the new 10.4 version got more specific to avoid those types of issues moving forward (audio drop outs) and this specific version flushed out those dual firewall scenarios? ...who knows, I'm just happy that its working again...

  • DancingGene Level 1 (0 points)

    I just wanted to confirm that a cold reboot solved the iTunes/AirShare problem for me on an older iMac, whereas a warm reboot did not. Thanks for the reminder about this cure-all.

  • prycefromhouston Level 1 (0 points)

    my airplay used to work flawlessly from my iMac and IPAD 2 but now that I upgraded to OS Lion and itunes 10.4 the iMac won't connect to airplay through itunes 10.4 (tries to connect for about 30 seconds but fails).  The IPAD 2 still connects to airplay almost instantaneously.


    I've done hard boots on both the airport express/airplay and the imac and it still fails to connect.

Previous 1 2 3 Next