Port 3689 - Ready for hare-care!!!

Question

Level 1

0 points

Port 3689 - Ready for hare-care!!!

Well, I believe I have tried just about everything to get my AppleTV (1st generation), to sync. It shows up in iTunes as a device, but when I try to sync it, I get the dreaded port 3689 error!

I have tried the following:

- Adding iTunes as a trusted service in Windows 7 firewall

- Disabling Windows 7 firewall

- Wired vs. Wireless (no difference)

- Giving AppleTV a static IP address

- Port forwarding

- Resetting AppleTV, resetting router, resetting everything!

- Even tried the same thing on another laptop, with the same results!

Nothing works! No matter what, I still get the "AppleTV not responding...port 3689...blah, blah, blah!

I think Apple has left us 1st generation AppleTV owners, in the dark. It seems like they just don't care anymore, and are only concerned about the latest generation products. The thing I really don't understand, is that this used to work flawlessly. Is the newer version of iTunes causing this problem? Is it the Windows 7 firewall causing the issue? Is it the fact that I switched from AT&T U-Verse to Comcast?

Am I just left with a 140GB paperweight?

Someone please help me!

Ray

Apple TV, Windows 7

Posted on Mar 12, 2012 6:43 AM

Reply

Answer 1

Jan 31, 2017 11:19 PM in response to rdonahue

Hi, I had the same iTunes error and it took me a very long time to resolve it so I'll post in the hopes of saving someone else the time. Open Terminal and run "ps aux | grep -i dns" (without the quotes). Make sure the mDNSResponder daemon is printed as output. In my case, there was "NoMulticastAdvertisements" shown as well, which interferes with Bonjour. If this is your problem, edit /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist to remove the line "<string>-NoMulticastAdvertisements</string>" and things should work better. This fix is for OS X but if you're running Windows you can just ensure that the Bonjour process is running correctly.

Reply

Answer 2

Mar 12, 2012 2:40 PM in response to rdonahue

Have you tried running the diagnostic on the ATV

Apple TV (1st generation): How to run diagnostics

support.apple.com/kb/HT1560

Reply

Answer 3

Mar 12, 2012 2:56 PM in response to rdonahue

Did the problem start when you switched to Comcast, do you use any security software on your PC, if you are using wifi have you tried using another channel.

Reply

Answer 4

rdonahue Author

Level 1

0 points

Mar 12, 2012 6:23 PM in response to Damian Smith1

I have not tried the diagnostics, but I will as soon as I have a chance. The odd thing is that iTunes recognizes the AppleTV, but when I try to sync it, I get the error message about port 3689. I don't think there is anything wrong with the device itself, but it can't hurt to run the diagnostics.

Reply

Answer 5

rdonahue Author

Level 1

0 points

Mar 12, 2012 6:28 PM in response to Winston Churchill

This is a very good question. The only things that have changed are 1) My laptop was reconfigured with Windows 7 and 2) I switched to Comast. I'm not sure when it happened, as I haven't actually used the AppleTV in a while. I do have Windows Firewall enabled, and I have OfficeScan for virus protection. I have tried switching to another laptop, and trying to sync, but it also gives the same error. The common factor is either Windows 7, or the Comcast router. Oh, and I did try plugging the AppleTV into a WET610 wireless bridge, so it doesn't work wired or wirelessly. Out of curiosity, what does changing the wireless channel have to do with it? In general, the wireless connectivity on the Comcast gateway, is not very good.

Reply

Answer 6

Mar 12, 2012 6:35 PM in response to rdonahue

What type of security are you using for wifi encryption.

Reply

Answer 7

rdonahue Author

Level 1

0 points

Mar 12, 2012 6:37 PM in response to Winston Churchill

WPA/WPA2-PSK-TKIP/AES

Reply

Answer 8

Mar 12, 2012 6:50 PM in response to rdonahue

Try disabling security temporarily for diagnostics, you can re-enable it straight away again if it doesn't help or look at the other settings available to you if it does.

Reply

Answer 9

rdonahue Author

Level 1

0 points

Mar 12, 2012 6:56 PM in response to Winston Churchill

Do you mean disabling the wireless security itself? I already tried disabling both the Windows firewall and the Comcast router's firewall, and still get the same error.

Reply

Answer 10

Mar 12, 2012 7:21 PM in response to rdonahue

No I mean the wifi security, the encryption, try turning it off.

Reply

Answer 11

rdonahue Author

Level 1

0 points

Mar 13, 2012 7:40 AM in response to Damian Smith1

I ran the diagnostics, and everything is fine. However, I am having a problem getting the firmware updated. It keeps saying No update available, try again later, or something to that effect. I am going to try the factory restore one more time, and then try to update the software again.

Nothing should be this difficult!

Reply

Answer 12

rdonahue Author

Level 1

0 points

Mar 13, 2012 7:48 AM in response to Winston Churchill

I tried setting security to Open (no password), and I still get the same error:

Reply

Answer 13

Mar 13, 2012 7:52 AM in response to rdonahue

Have you seen this Apple support article about your issue

http://support.apple.com/kb/TS2709

Reply

Answer 14

rdonahue Author

Level 1

0 points

Mar 13, 2012 7:56 AM in response to Damian Smith1

Yes, seen it several times, and tried everything mentioned, and still get the same error. I even tried setting my wireless security to None, and turning off both the Windows firewall, and the router's firewall.

Reply

Answer 15

Oct 13, 2012 8:11 AM in response to rdonahue

I recently had this same problem pop up. I ended up assigning the Apple TV a fixed local IP address through my router (Cisco Valet). Once I'd done that through the router's interface, I went into the Apple TV Network Setup and ran the manual configuration. With the static IP everything is working peachy. I think the problem has to do with the DHCP assigning conflicting IP addresses to the Apple TV, but I'm not sure. In any case, this solution worked for me.

Reply