UPDATED - new BTMM issue : Back to my Mac DNS issue??
On Thu, Apr 3, 2014 at 7:05 AM, LuKreme wrote: > On 02 Apr 2014, at 16:24 , Jeff Weinberger > wrote: > > "Back to my Mac isn't working properly because the DNS server is not > responding" and suggests I contact my internet service provider for a > different DNS server address. > > What are your DNS servers set to? > > Does B2MM work despite the message? > Sorry - missed this emailThey are the defaults for my ISP: 76.14.0.8/9(all other services that use DNS - like web browsing - work just fine) and no BTMM does not work UPDATE : I asked my new ISP to reconnect my line to my old ISP (they can access the cable closets in my building). They did, and BTMM still did not work. It worked as recently as a week ago with my old ISP. I have to conclude that either Apple updated something behind the scenes that I don't know about or something in changing the network knocked this out of whack. I don't know where to start to look for a resolution...any suggestions are very much appreciated!! Jeff ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: UPDATED - new BTMM issue : Back to my Mac DNS issue??
The only thing I can think of is that it sounds like Back to My Mac is asking the DNS to resolve the name of some Apple server, and your ISPs DNS either has no idea where it is or has it blocked. I would manually set my the DNS on my Mac to a public server, like 4.4.4.4 or open DNS, and see if Back to My Mac likes that better. My second attack would be to Google the syndrome, and my third would be to wireshark the connection, which is quite laborious. > On Apr 3, 2014, at 4:35 PM, Jeff Weinberger wrote: > >> On Thu, Apr 3, 2014 at 7:05 AM, LuKreme wrote: >> On 02 Apr 2014, at 16:24 , Jeff Weinberger wrote: >> > "Back to my Mac isn't working properly because the DNS server is not >> > responding" and suggests I contact my internet service provider for a >> > different DNS server address. >> >> What are your DNS servers set to? >> >> Does B2MM work despite the message? > > > Sorry - missed this emailThey are the defaults for my ISP: 76.14.0.8/9 > (all other services that use DNS - like web browsing - work just fine) and no > BTMM does not work > > UPDATE : > > I asked my new ISP to reconnect my line to my old ISP (they can access the > cable closets in my building). They did, and BTMM still did not work. > > It worked as recently as a week ago with my old ISP. I have to conclude that > either Apple updated something behind the scenes that I don't know about or > something in changing the network knocked this out of whack. > > I don't know where to start to look for a resolution...any suggestions are > very much appreciated!! > > Jeff > > > ___ > MacOSX-talk mailing list > MacOSX-talk@omnigroup.com > http://www.omnigroup.com/mailman/listinfo/macosx-talk ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: UPDATED - new BTMM issue : Back to my Mac DNS issue??
On Thu, Apr 3, 2014 at 7:31 PM, Macs R We wrote: > The only thing I can think of is that it sounds like Back to My Mac is > asking the DNS to resolve the name of some Apple server, and your ISPs DNS > either has no idea where it is or has it blocked. > > I would manually set my the DNS on my Mac to a public server, like 4.4.4.4 > or open DNS, and see if Back to My Mac likes that better. > I have tried Google's public DNS service (8.8.8.8 and 8.8.4.4) to no avail. > My second attack would be to Google the syndrome, > I'll keep trying, but so far, only a bunch of threads on the Apple support discussion groups that all conclude that the solution is to remove something called BroadBand Tuner - which I don't have installed (verified by their instructions) > and my third would be to wireshark the connection, which is quite > laborious. > I don't know this one, but I'll give it a try - can't be worse than the 10-15 hours I've spent with other miscellaneous non-working answers! Thank you for your help! > > > On Apr 3, 2014, at 4:35 PM, Jeff Weinberger > wrote: > > On Thu, Apr 3, 2014 at 7:05 AM, LuKreme wrote: > >> On 02 Apr 2014, at 16:24 , Jeff Weinberger >> wrote: >> > "Back to my Mac isn't working properly because the DNS server is not >> responding" and suggests I contact my internet service provider for a >> different DNS server address. >> >> What are your DNS servers set to? >> >> Does B2MM work despite the message? >> > > > Sorry - missed this emailThey are the defaults for my ISP: > 76.14.0.8/9(all other services that use DNS - like web browsing - work just > fine) and > no BTMM does not work > > UPDATE : > > I asked my new ISP to reconnect my line to my old ISP (they can access the > cable closets in my building). They did, and BTMM still did not work. > > It worked as recently as a week ago with my old ISP. I have to conclude > that either Apple updated something behind the scenes that I don't know > about or something in changing the network knocked this out of whack. > > I don't know where to start to look for a resolution...any suggestions are > very much appreciated!! > > Jeff > > ___ > MacOSX-talk mailing list > MacOSX-talk@omnigroup.com > http://www.omnigroup.com/mailman/listinfo/macosx-talk > > ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: UPDATED - new BTMM issue : Back to my Mac DNS issue??
Adding some info if this helps - and maybe an additional question: I've noticed that all of the IPv6 parameters and settings are blank on all of my ISP settings (their router, and it's missing in their docs). Is it possible that their DNS servers (the ones I'm using) don't support IPv6, and if they don't could this be an issue? It looks like BTTM is looking for an IPv6 address Log file pasted below... Thank you! On Thu, Apr 3, 2014 at 8:39 PM, Jeff Weinberger wrote: > On Thu, Apr 3, 2014 at 7:31 PM, Macs R We wrote: > >> The only thing I can think of is that it sounds like Back to My Mac is >> asking the DNS to resolve the name of some Apple server, and your ISPs DNS >> either has no idea where it is or has it blocked. >> >> I would manually set my the DNS on my Mac to a public server, like >> 4.4.4.4 or open DNS, and see if Back to My Mac likes that better. >> > > I have tried Google's public DNS service (8.8.8.8 and 8.8.4.4) to no > avail. > > > > >> My second attack would be to Google the syndrome, >> > > I'll keep trying, but so far, only a bunch of threads on the Apple support > discussion groups that all conclude that the solution is to remove > something called BroadBand Tuner - which I don't have installed (verified > by their instructions) > > > >> and my third would be to wireshark the connection, which is quite >> laborious. >> > > I don't know this one, but I'll give it a try - can't be worse than the > 10-15 hours I've spent with other miscellaneous non-working answers! > > > Thank you for your help! > > >> >> >> On Apr 3, 2014, at 4:35 PM, Jeff Weinberger >> wrote: >> >> On Thu, Apr 3, 2014 at 7:05 AM, LuKreme wrote: >> >>> On 02 Apr 2014, at 16:24 , Jeff Weinberger >>> wrote: >>> > "Back to my Mac isn't working properly because the DNS server is not >>> responding" and suggests I contact my internet service provider for a >>> different DNS server address. >>> >>> What are your DNS servers set to? >>> >>> Does B2MM work despite the message? >>> >> >> >> Sorry - missed this emailThey are the defaults for my ISP: >> 76.14.0.8/9 (all other services that use DNS - like web browsing - work >> just fine) and no BTMM does not work >> >> UPDATE : >> >> I asked my new ISP to reconnect my line to my old ISP (they can access >> the cable closets in my building). They did, and BTMM still did not work. >> >> It worked as recently as a week ago with my old ISP. I have to conclude >> that either Apple updated something behind the scenes that I don't know >> about or something in changing the network knocked this out of whack. >> >> I don't know where to start to look for a resolution...any suggestions >> are very much appreciated!! >> >> Jeff >> >> 4/3/14 8:54:03.165 PM racoon[3070]: Connecting. 4/3/14 8:54:03.166 PM racoon[3070]: IPSec Phase 1 started (Initiated by me). 4/3/14 8:54:03.178 PM racoon[3070]: IKE Packet: transmit success. (Initiator, Aggressive-Mode message 1). 4/3/14 8:54:03.178 PM racoon[3070]: Connecting. 4/3/14 8:54:03.178 PM racoon[3070]: IPSec Phase 1 started (Initiated by me). 4/3/14 8:54:03.182 PM racoon[3070]: IKE Packet: transmit success. (Initiator, Aggressive-Mode message 1). 4/3/14 8:54:03.187 PM awacsd[102]: Could not find token for fd5d:56f5:02d1:26a0:a108:b83b:6d69:69e2 4/3/14 8:54:06.362 PM racoon[3070]: IKE Packet: transmit success. (Phase 1 Retransmit). 4/3/14 8:54:06.362 PM racoon[3070]: IKE Packet: transmit success. (Phase 1 Retransmit). 4/3/14 8:54:06.363 PM awacsd[102]: Could not find token for fd5d:56f5:02d1:26a0:a108:b83b:6d69:69e2 4/3/14 8:54:09.660 PM racoon[3070]: IKE Packet: transmit success. (Phase 1 Retransmit). 4/3/14 8:54:09.660 PM racoon[3070]: IKE Packet: transmit success. (Phase 1 Retransmit). 4/3/14 8:54:09.660 PM awacsd[102]: Could not find token for fd5d:56f5:02d1:26a0:a108:b83b:6d69:69e2 4/3/14 8:54:12.955 PM racoon[3070]: IKE Packet: transmit success. (Phase 1 Retransmit). 4/3/14 8:54:12.955 PM racoon[3070]: IKE Packet: transmit success. (Phase 1 Retransmit). 4/3/14 8:54:12.956 PM awacsd[102]: Could not find token for fd5d:56f5:02d1:26a0:a108:b83b:6d69:69e2 4/3/14 8:54:25.162 PM racoon[3070]: IKE Packet: transmit success. (Phase 1 Retransmit). 4/3/14 8:54:25.162 PM racoon[3070]: IKE Packet: transmit success. (Phase 1 Retransmit). 4/3/14 8:54:25.162 PM awacsd[102]: Could not find token for fd5d:56f5:02d1:26a0:a108:b83b:6d69:69e2 4/3/14 8:54:37.028 PM racoon[3070]: Phase 2 negotiation failed due to time up waiting for Phase 1. ESP fd5d:56f5:2d1:26a0:a108:b83b:6d69:69e2[0]->fd5d:56f5:2d1:26a0:40c2:1707:f3ea:5737[0] 4/3/14 8:54:37.250 PM racoon[3070]: Phase 2 negotiation failed due to time up waiting for Phase 1. ESP fd5d:56f5:2d1:26a0:40c2:1707:f3ea:5737[0]->fd5d:56f5:2d1:26a0:40c2:1707:f3ea:5737[0] 4/3/14 8:54:41.125 PM racoon[3070]: IKE Packet: transmit success. (Phase 1 Retransmit). 4/3/14 8:54:41.126 PM racoon[3070]: IKE Packet: transmit success. (Phase 1 Retransmit). 4/3/14 8:54:41.126 PM awacsd[102]: Could not find token for fd5d:56f
Re: UPDATED - new BTMM issue : Back to my Mac DNS issue??
You need to turn on "Find My Mac" for this machine. The "token" it's failing to find is the Find My Mac ID token. This seems to be something new in 10.9 as others have noted. Not sure if this should be considered a bug or a feature... 4/3/14 8:54:59.513 PM racoon[3070]: IKE Packet: transmit success. (Phase 1 Retransmit). 4/3/14 8:54:59.514 PM awacsd[102]: Could not find token for fd5d:56f5:02d1:26a0:a108:b83b:6d69:69e2 4/3/14 8:55:09.121 PM NetAuthSysAgent[4793]: ERROR: AFP_GetServerInfo - connect failed 64 4/3/14 8:55:09.123 PM sharingd[209]: SDSharePointBrowser::handleOpenCallBack returned 64 4/3/14 8:55:12.504 PM racoon[3070]: Phase 2 negotiation failed due to time up waiting for Phase 1. ESP - Steve Freeman, Indie IT -- View this message in context: http://mac-os-x.10953.n7.nabble.com/UPDATED-new-BTMM-issue-Back-to-my-Mac-DNS-issue-tp35824p35874.html Sent from the OmniGroup - MacOSX-General mailing list archive at Nabble.com. ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
