Spoke to soon again. Same issue. No content available. Omg I am so hacked right now.
You all tried rebooting the Apple TV after updating to the new iTunes?
I, too, am experiencing this problem. I've narrowed it down a bit. When iTunes starts with any sort of sharing enabled it opens IPv4 and IPv6 TCP sockets to listen for connections. About 7-9 seconds after starting the IPv4 socket gets closed for whatever reason.
I really hope Apple gets around to fixing it soon. In the meantime I've found a workaround. Unfortunately you have to do it every time you restart iTunes.
1) Disable sharing (iTunes -> Preferences -> Sharing)
2) Disable Home Sharing (Advanced -> Turn Off Home Sharing)
3) Re-enable Sharing and/or Home Sharing.
This seems to work for me as long as I keep iTunes running. After you turn off sharing (steps 1 & 2) it closes the sockets. When you re-enable it in step 3 they open back up and stay open as you'd expect.
You can watch all this happening by opening Terminal.app and running the following:
while true; do clear && lsof -i -n -P | egrep '^iTunes|^COMMAND' && sleep 1; done
I tried dtrussing iTunes while it was creating and tearing down sockets, but there were no obvious errors. Really frustrating.
Same problem on my 17" Quad. Really a bummer since me and my wife watch so much content on the Apple TV. I thought I was going nuts until looking in to the forums. My PC Tower is streaming just fine, but I have two G1 Apple TVs and I cant stream from the MBP to either one of them. I must have reconnected and connected 50 times.
Whats even more bizarre...one out of every 100 times it just starts WORKING. Then I'll watch an episode of a TV show, and after that episode it quits. Gives the "Cannot connect to this iTunes library. Check Network Config" garbage error. IP Stack on both is fine, and the Apple TV can get Youtube and iTunes store content with no problem.
Clearly some kind of OS Build issue.
For fun I dumped iTunes and chased down the extension in Core Services, etc and then did a complete iTunes reinstall. No Go.
Tried killing the .xml file and rebuilding the library. No Go.
I was sure that the update today was specifically to address the problem. Nope. I can't believe we haven't heard anything from Apple on this one. This had to have been passed to support engineers by Feb 25-26 so there has to be a major patch coming for this.
WIERD![]()