Q: Home Sharing drop out with Apple TV2

I´m gonna try this tell you if it worked

I've been troubleshooting with apple for a few days now. Just talked to the tech again a little while ago, and what they want us to try is to plug the ATV directly into the Ethernet jack of the computer and leave the computer connected to the Internet via wifi. Then we will see in the morning if the home sharing stays connected this way in order to eliminate it being a router issue, which I myself do not think it is. So I will try this just for the sake of argument and see what happens.

Upgraded my Apple TV 2 as well to 5.0 and just noticed this issue for the first time.

It seems that this fix worked for me... restart the modem and router completely. Since doing this, my movie that I am watching has not stopped yet under home sharing. It was disconnecting after five minutes of connection.

Thanks for posting this fix -- so far, so good!

Not really done anything here but my sharing has stayed connected for the past 3 days on both of my ATVs

Fingers crossed.

I've been struggling with this over the past year, it seems like.  For the most part I've lived with disconnecting/reconnecting Home Sharing on the ATV, but after the latest update it got so bad I could hardly watch anything over 10 mins.  I decided to heavily dig into the issue.   Pretty much did everything in this thread:  Uninstalled & Reinsalled Bonjour/iTunes (Win7 x64), connected ATV via hard wire, messed with all sorts of wireless and network settings in my router (DLink DIR-655), and I even bought a new ATV3.  There was no fix in sight.  Friday I broke down and bought a new wireless router and haven't had a problem since.  This tells me there was a setting or something in the router causing an issue.  I'm curious as to what it is/was, but am extrememly happy I no longer have drop-outs on my ATV!

I have the same router DLink DIR-655 and the drop outs drove me crazy. Luckily, I had a wired connection going to my blu-ray player. Just added a switch and problem went away. I'm glad I found this post I thought I had a faulty ATV 2.

Thanks for sharing.

For those who are wondering, I meant to note that I bought a Cisco Linksys E4200 to replace the DLink DIR-655.

Hello Everyone..! did someone fix this problem I just update my ATV to the new IOS and bang..!! keep disconnecting after a few minutes of play.

I didnt have this issue until I update my  ATV2 and the Itunes on my PC..

I am having the same issues with a D-Link router.

My iMac is connected via wifi and my Apple TV was connected via Wifi

I changed the ATV to wired but still getting the drop outs.

Unfortunately due to the location of my iMac, it will have to remain wireless, although it is only about 5 metres away from the router.

I am going to try swapping out the wireless router today and see if that helps.

Will report back in a few days

I tried replacing my router again Friday and the dropout did not occur for over 24 hours. But when I woke up this morning home sharing had disconnected again. I really had my hopes up yesterday when I woke up and it was still connected but was disappointed again this morning. This is becoming VERY aggrivating!

@spma3, I'm a little confused about the port forwarding. Do I forward the ports to the Apple TV or to the computer? I ask this because if I am forwarding to the apple tv's ip address, then how do I go about forwarding to multiple ATV's?

Thanks for your help!

Although I have the ports forwarded to the IP Address of my ATV, it shouldn't matter if the port is forwarded to the computer or ATV. It's opening the communication from ITunes Servers through your router to your iTunes account on your computer. Try forwarding to your computer and if for some reason it doesn't work, try doing it to one of the ATV's. Once a port is forwarded, its open and can't be forwarded to another address as well.

If your computer running iTunes is Windows7, also try disabling IPv6 protocol. This seemed to work for other people from another thread.

And you say to put port 3689 on UDP, correct?

yes because I had it TCP and it didn't work.