Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

4 points

iTunes 10.1 for Mac breaks firewall?

I just upgraded to iTunes 10.1 this morning and something interesting has happened. Now, every time the application starts up, a window appears saying

"Do you want the application "iTunes.app" to accept incoming network connections?"

Well, I do. I checked the firewall and it's already allowing incoming connections. No matter how many times I toggle this on and off, every time I restart the application, it still asks me.

Unfortunately, I cannot delete an entry in the firewall area, so I'm wondering how I can do this. Wipe out the entires in the firewall area to "restart" fresh so when I click a box, it won't repeatedly ask me again.

Thanks!

Mac Pro 8-Core; 16GB, Mac OS X (10.6.5), iTunes 10.1

Posted on Nov 12, 2010 11:55 AM

45 replies

0tter

Level 1

0 points

Nov 14, 2010 2:23 AM in response to yasmin.k

Yep, the standalone installer is the way to fix it.

Brett C

Level 1

15 points

Nov 14, 2010 11:54 AM in response to R. Yannetta

I had this same problem after upgrading to iTunes 10.1

removing com.apple.alf.plist, reinstalling iTunes, etc seems to have fixed the problem for me.
thanks

Nov 14, 2010 7:39 PM in response to R. Yannetta

I did the re-install thing the last time this happened. This issue has been going on for years. Seriously? Come on Apple, this is your software, your OS, your hardware. Shame on you for not fixing this yet.

AusBoy

Level 1

0 points

Nov 15, 2010 4:50 AM in response to R. Yannetta

I just deleted the entry from the firewall dialog box and it re-added it again and hasn't caused problems since.

Nov 15, 2010 5:55 PM in response to Glenn Carter

Important (albeit possibly dumb) question. I have had to transfer my iTunes library from PC to PC several times and finally from PC to Mac. Every time, I have lost my play counts. If I uninstall then reinstall iTunes, will I lose those numbers? It seems trivial, but it really bugs me that I keep losing my play count tallies haha

Nov 15, 2010 6:13 PM in response to jennabobenna

Jenna, information like Play counts is stored within your iTunes database, NOT the application itself. So if you simply re-install the app, all of your metadata should still be there. Cheers!

Adrian M

Level 1

81 points

Nov 16, 2010 12:24 AM in response to R. Yannetta

Just downloading and installing 10.1 fixed it for me. No messing with firewall settings, deleting old iTunes first, or rebooting.

The codesign check showed good after the install.

Thanks for that tip!

Message was edited by: Adrian M

pnanko

Level 1

4 points

Nov 16, 2010 7:44 AM in response to R. Yannetta

FYI, I only encountered this problem when my son upgraded iTunes from his non-admin account on shared house Mac. Lesson-learned, 'edict', I mean: direct non-admins to NOT do upgrades themselves, but to wait for admin account to do it.

medgirl

Level 1

12 points

Nov 16, 2010 8:44 AM in response to pnanko

pnanko wrote:
FYI, I only encountered this problem when my son upgraded iTunes from his non-admin account on shared house Mac. Lesson-learned, 'edict', I mean: direct non-admins to NOT do upgrades themselves, but to wait for admin account to do it.

That's probably a good rule of thumb in general, but this happened to me on all of my Macs with the last iTunes update. I'm the admin on all of them, and actually the only account on two of them.

trailer

Level 1

0 points

Nov 19, 2010 1:04 AM in response to medgirl

I had this problem with 10.1 too. (Also on a previous update but I can't remember which one). Simply downloading the stand alone installer and installing straight over the top of the 10.1 already installed solved the issue.

Nov 25, 2010 12:21 AM in response to trailer

I also had this firewall problem with 10.1. I tried deleting the firewall setting the problem came back. Next I downloaded installed the stand alone v10.1. I didn't mess with permissions, or delete old iTunes. Simply downloading the stand alone installer and then installing it solved the issue.