This discussion is archived
17612 Views 131 Replies Latest reply: Jun 29, 2009 7:22 AM by openthreads
Currently Being ModeratedMar 28, 2009 3:53 PM (in response to Patrick Mau)Neat idea.
But it doesn't work in my setup. I disconnected all my home Macs so nothing from my home network was active on MobileMe. This did NOT cause my Time Capsule to show up outside my home network.
Apple ... please make this work.
(Yes, I submit feedback to the official Apple page.)MBP unibody (late 2008) 2.8; MBA (original); Mac mini (original), Mac OS X (10.5.6), Dell 30" Display; Apple 24" LED Cinema; iPhone 3G/16; TV; TimeCapsule 1 TB
Currently Being ModeratedMar 28, 2009 3:59 PM (in response to Patrick Mau)Hi Patrick, I understood what you're trying to say. I've seen this bug as well. Both the AX and your Mac Pro are trying to use port 4500 for BTMM and that's why the packets for your AX are being redirected to the Mac Pro. This appears to be a bug in the AX. You may be able to work around the issue by rebooting the AX, or by rebooting the Mac Pro. Then hopefully one of them will get port 4500 and the other will notice that 4500 is already in use and choose another port to use. Hopefully Apple will fix this issue in a future firmware update for the AX.MacBook Pro, Mac OS X (10.5.6)
Currently Being ModeratedMar 28, 2009 11:46 PM (in response to Snoop Dogg)Snoop Dogg
"I hope somebody understood what I was saying, but I doubt it ..."
was intended to sound like:
"I hope somebody *at Apple* understood what I was saying, but I doubt it ..."
I did not mean people in this thread or forum, but the guys at Apple I tried to explain the issue to... Sorry, if that was not clear from my post.Mac OS X (10.5.6)
Currently Being ModeratedMar 29, 2009 8:04 PM (in response to EvilHomer80)Well it's been weeks since I opened my trouble ticket with Apple regarding this issue. They were very communicative at first with lots of follow up calls, etc. Now there is complete silence this usually means that Apple has no clue as to why this isn't working yet or more likely perhaps its another MobileMe ooops!!! Aren't we getting used to that?? Sigh.iMac Extreme, Mini 2.0ghz, MBPro Early 2008, Mac OS X (10.5.4)
Currently Being ModeratedMar 31, 2009 6:03 PM (in response to Patrick Mau)Interesting, I think you may be wright. I have at home 1 time capsule connected to a Linksys AM200 ADSL2+ modem. The modem is setup to be in bridge mode only. To this time capsule I have connected 2 Airport Extremes using ethernet cables. I can always access 2 computers and the 2 airports from outside, but I can never access the time capsule. Please ask for more information about my setup if you want.MacBook Pro 17", Mac OS X (10.5.6)
Currently Being ModeratedApr 3, 2009 7:43 PM (in response to dwmreg64)I called AppleCare last weekend and explained my problem with needing my Actiontec router to be first and the Time Capsule behind it to be bridged. The representative was very patient and understood what I was saying. (A rarity -- maybe more common at Apple, but a rarity none the less.) He didn't hurry me, asked very intelligent questions, could tell that I had spent a lot of time on this, and wrote it up well for the engineers.
Today, he got back to me, about six days after my initial report. He said that there was no immediate fix, but that the engineers were aware that people were experiencing difficulties having their Time Capsules seen outside their home networks when they were not the first router in line, and they understood that for some installations -- like MOCA FIOS installations -- it was very difficult to make the Time Capsule first. He didn't guarantee a fix, but said if it came it would be in the form of a Time Capsule firmware update.
While it would have been nicer for him to give me a solution (which at this point doesn't exist) or to tell me a date certain when this would be fixed (which may also be unknown), I truly appreciated that he got back to me, acknowledged that Apple was receiving reports of this, and said they are genuinely trying to fix it.
I was very satisfied with the way my original issue was understood and escalated. I can't remember a more pleasant, productive discussion, at least not in the last few years, with a technical service representative (even at Apple).
I'd look for a fix within a few months, if not sooner, in the same kind of way that the original MobileMe moved from problems to reliable in a few months and the original BackToMyMac took a while to iron its kinks out.MBP unibody (late 2008) 2.8; MBA (original); Mac mini (original), Mac OS X (10.5.6), Dell 30" Display; Apple 24" LED Cinema; iPhone 3G/16; TV; TimeCapsule 1 TB
Currently Being ModeratedApr 4, 2009 7:16 AM (in response to Linda Custer)Linda,
Your post is the most promising info I have heard to date about this. I have spent way too much time trying to remotely access my TC and have had zero luck.
Thank you very much for the update.
Currently Being ModeratedJun 7, 2009 7:21 PM (in response to Mrmgee)I'm still waiting. I'm pretty sure the fix would require a firmware update to the Time Capsule, and that is something that I don't think has come out lately.
I don't believe there is any fix yet -- at least not one I'm aware of.
I've got my fingers crossed.MBP unibody (late 2008) 2.8; MBA (original); Mac mini (original), Mac OS X (10.5.6), Dell 30" Display; Apple 24" LED Cinema; iPhone 3G/16; TV; TimeCapsule 1 TB
Currently Being ModeratedJun 9, 2009 4:52 AM (in response to Linda Custer)Same here, I think I tried everything I could possibly think of for the past 2 months but still unable to get it to work. I agree that a firmware update is probably the last possible way to fix this. Crossing fingers too...
Actually I was hoping the recent rumor of MobileMe V2 could be announced at Apple's WWDC09 yesterday would be true and would fix it !Imac, Mac OS X (10.5.7)
Currently Being ModeratedJun 23, 2009 6:33 PM (in response to stdude)The update Apple issued today for the Time Capsule totally fixed this for me.
Currently Being ModeratedJun 29, 2009 7:22 AM (in response to openthreads)Looks like firmware 7.4.2 update fixed this issue for both my Time Capsule and Airport Extreme:
http://discussions.apple.com/message.jspa?messageID=9733258Macbook Pro 17" unibody (mid 2009), Mac OS X (10.5.7)