Airport 'unknown error occurred (-15000)'

I've had no luck with this issue.

Running a windows laptop, XP, with latest itunes and get this same error however another windows machine on the same network running vista can connect and use the airport express speakers just fine.

After I updated iTunes to version 8.0.2, I set the IPv6 back to 'Automatically' and have had no issues with AirTunes since. Of course, your mileage may vary.

For sure... I still have the the problem in iTunes 8.0.2 and Mac OS X 10.5.6.
Works when disabling IPv6 so thanks for this tip!

i tried all the tips and things within this thread myself and im experiencing the (-15000) error.

This was working solid for the past 3-weeks when i first set it up.
i restored the AEX to default/factory settings. no avail.

this all started when i replaced the speakers connecting to the AEX.

in the past 3-weeks all my AirPort devices have been having some random, occurring issues ...hmmmmm

Hi;

It seems to happen when something being synched over the network (like the Apple TV). When the file transfer's done, everything seems to work normally again. If you're using an ATV, either leaving it to fully synch, or manually doing it might help.

Good luck!

Hi,

After receiving the -15000 error, I noticed my mac had logged onto my internet connection via airport express rather than directly through my wireless modem. I switched it back to the wireless modem and hey presto, no -15000 error. I know this may not be the solution for all -15000 errors but worth a try if you have a similar set up to mine.

Cheers.

I've been dealing with this -15000 issue all morning and this is the only fix that worked for me.

But I have the same question as ShaunFromScotland. Does changing the TCP/IP setting to "Off" bugger up any other program?

Kindly share some wisdom.

This is usually network related. For example, if I am running a large network file copy and try to begin playing something over Airtunes, I usually get a -15000 error, particularly if the file copy is over wireless. If I stop the copy, start the Airtunes session and then start the file copy again, it's fine. It seems to be that there is a small timeout on the initial airtunes connect. I suspect all the "enable/disable IPV6" etc. things are just red herrings.

I suspect all the "enable/disable IPV6" etc. things are just red herrings.

Disagree. Disabling and re-enabling IPV6 robustly fixes and reintroduces the problem for me. No other action touches it.

I wondered if this problem derived from the 10.5.7 update, as the problem began within 24 hours of installation of the update, in the context of more than a year of unproblematic operation. Still, I see the posts in this thread long pre-date the update.

Hi - I don't know what to make of this but someone will.

My remote speakers work just fine when the computer I am playing ITunes on is connected to my network via AirPort.

_As soon as I connect the CAT5 network_ cable into the G5 I get the 15000 error message.

Who can make something of that?

Cheers

I just switched IPv6 OFF on my Ethernet connection in SYS Pref>Network>Ethernet>Advanced and it seems to have certainly fixed that problem.

TS

I am from the turning IP v6 off worked for me crowd thanks
This is found in System Preferences -> Network -> Airport -> Advanced... -> TCP/IP

Hi,

I just recently had the same problem and I found a way to fix it on OSX. Go to System Preferences=>Sharing (Folder under Internet and Security)=>Firewall tab. Make sure that you have the iTunes Music Sharing box checked or try turning off the firewall. This worked for me...hope it helps.

I was getting this error (An unknown error occurred (-15000)) out of the blue after running airport express without a problem for about a month. I took a look at the log in the Airport Utility (Double click on your Airport Express>click the Advanced button>Logs and Settings). I noticed a bunch of entries for the date/time I was getting the error:
Aug 31 20:55:15 3 AirTunes time sync receive error: -6730
Aug 31 20:55:18 3 AirTunes too many time sync negotiate failures: 64/0/64
From there I clicked on the Airport button>Airport Express tab. I unchecked the box labeled "Set time automatically", and it is working fine now. I'm not sure why airport express needs to know what time it is, perhaps this is how it knows when to check for updates? Maybe there was some sort of glitch with apple's time server, so I'll try to re-enable this at some point in the future.

I had same issue, followed instructions from different Apple KB articles but issue persisted...

I found the solution though.

My Airport Express was setup to joined my Time Capsule wireless connection... I turned the wireless off on my Express and plugged wire between my TC and my APX -> issue solved