Connection to www.logmein.com times out...

No problem here.

This doesn't help you, and I can't think what to suggest you try to change on your Mac from what you've said is/isn't working (and assuming every other website is ok on your Mac, just not LogMeIn) but it's working for me too.

Can you get to https://secure.logmein.com/home.asp?lang=en instead; that is the page I have bookmarked to log in to at LogMeIn. If it's some funny DNS lookup (or proxy/cache) issue, maybe using that different hostname and HTTPS might get you around it?


ted.h.

As it happens, there's another thread about the same issue in the Safari forum. What I suggested in there, and seems to have worked, is to try using the IP address for the LogMeIn web server and see if it is then accessible. See if this works for you too: https://72.5.76.193/home.asp?lang=en

If that numeric address (which is what a lookup of secure.logmein.com resolved to for me) works, then at least we will have narrowed down the problem to an incorrect or stale DNS lookup for LogMeIn's website on your Mac. That doesn't explain why it's started happening, but at least it's a step forward...


ted.h.

Okay, I guess I would say it was a DNS issue, in as much as when I look up www.logmein.com (or secure.logmein.com) I get it resolved as 72.5.76.193 - and accessing it at that address is working fine for me - whereas it looks like you are getting it resolved as 69.25.20.193 and accessing the website at that address is not working for you. I'm sure you know this, but just because some box responds to a ping doesn't mean it has a web server running on it (and not necessarily the web server you think you are accessing even if it does). My theory is that LogMeIn moved their server from the 69. address to the 72. address some time in recent days, and some people (either their workstations or their ISP) are still using a cached lookup for that server where it isn't anymore.

If you didn't do so earlier, just to humour me please try accessing the LogMeIn website via the IP-address URL I posted last time and see if you get a different result.

Alternatively (because it looks like the thing that needs to be fixed), how do you explain your Mac - from which LogMeIn isn't accessible - resolving their server as 69.25.20.193 while mine - from which it is accessible - resolves it as 72.5.76.193?

Sorry I don't have any other ideas other than it is an incorrect/stale DNS lookup.

ted.h.

Okay, so what is likely happening (when you enter the IP-addressed URL for LogMeIn.com) is it is successfully getting to the LogMeIn web server, then redirecting to secure.logmein.com, which (of course, and unfortunately) is still resolving to the wrong/old/incorrect address on your Mac, then you're still going nowhere at the end of it all.

I use a 3rd party DNS service, rather than the DNS provided by my ISP, so if you can change the address(es) used for DNS on your Mac - or on your router instead if you want to change all the machines on your local LAN - to the ones offered by http://www.opendns.com (the DNS server IP addresses, and how to configure for various devices, are linked off that page) you should then be getting exactly the same DNS lookups as I am (and that should mean the current/correct address for LogMeIn.com).


ted.h.

Glad it's working for you now, but (1) you and I are presumably still getting different IP addresses for that server, and (2) I don't have my MTU at 1472 (it's (still) whatever the maximum is for my cable internet ISP anyway - ie 1492, 1500, whatever it is, more than 1472 anyway).

All good fun, isn't it 😉

ted.h.

I have exactly the same problem here...
At the end, have you discovered if it's a matter of DNS or the thing in the router?
with the same laptop at work, www.logmein.com works ok, at home, doesn´t work.
Connecting to a Centos in another location with my FreeNX works (works there I mean, I am inside my router at home).
About DNS, when pinging www.logmein.com is 69.25.20.193 as well)

thank you very much!
Gari