Safari will not open logmein.com

I have the same problem with the safari and logmein site, i have succesfully open the site 2 or 3 times the last week even trying each day.

Curiously when i try to access to logmein site using Firefox i have the problem that FF keeps trying to load the starting page of the site, and never finishes, i dunno if this is a leopard related problem by the network libraries or an specific browser problem.

Someone has posted what sounds like the same problem in the Tiger forum. Here's what I posted there, in case it helps at all (I don't know yet whether it helped for the people in that other thread, but it'll only take a minute for someone affected to try it):

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.

Well, i tried to reach the site typing the exact URL you give me, same problem both browsers, im gonna write to logmein support asking a solution, ill keep in touch to the topic, i think i would trace some errors in the browsers or trace a http session, as soon i got a progress as ill give u news

Well, i was browsing in the LMI support forums (by a windows computer hahaha), and the official LMI answer is that the problem is within leopard, any people that upgraded Leopard from a a tiger Mac can work with no problem but clean Leopard installations are not possible to access LMI site or even use the application, so by now the only way to work with LogMeIn is using a Parallels or VMWare Fusion Machine and load the browser by a Windows or any Linux Machine.

Any news plz feed the forum

Could it be some DNS issue (ie perhaps the server has moved but some ISPs still have stale DNS entries pointing to a now-unhelpful IP address)?

Try this URL - https://72.5.76.193/home.asp?lang=en - and see if you get anything different. You should get a warning about the certificate being unable to be verified - because you are using the IP address rather than the correct domain name for the server - but you should get the page displayed successfully.

Outside of that giving a pointer to the nature of the problem, I don't know what to suggest I'm afraid. It's definitely working for me (Safari, Camino and Firefox on OS X 10.4.11), so I can only guess it is working for most people out there BUT from the posts in here and the other thread in the Tiger forum definitely affecting some people on Macs and 100% repeatable failure for them to that site, regardless of which browser they are using on their Mac.


ted.h.

It works on!!!!

Thanks ted, the IP was very useful, the only doubt i have left its why windows computer recognizes the correct IP's because when you use another OS the browsers works well with the DNS names.

Thanks again, hope the address works for the rest of the guys having the same issue.

I've read a few threads about Leopard keeping stale DNS entries (and needing to be manually flushed by some folks periodically to encourage it to do new lookups from their ISP's DNS server, rather than coughing-up potentially out-of-date entries they had looked up earlier and cached). I don't know much specifically about the issue (none of my Macs have made the leap forward to Leopard yet), but maybe do a forum search along those lines and see if it turns up anything helpful.

On another tack, is your Mac using the same DNS server(s) as your other machines on your LAN (ie have you specified a different DNS between the working machines and non-working machines? FWIW, I have had sporadic issues here with my ISP (a very large one in Australia) having their DNS swamped and become intermittently non-responsive, so a month or so ago I moved across to use DNS servers provided by the people at http://www.opendns.com - I have their DNS server addresses specified in my router, and then all the Macs (and sundry other computers, games consoles, etc) pick these up by default. If the issue turns out to be that your ISP has stale lookup entries for LogMeIn.com (and it seems that someone does - the question is whether it is a cache on your Mac or at your ISP that is the source of the stale lookup), maybe try changing it, at least temporarily, rather than needing for force your way to LogMeIn.com by the direct IP address.


ted.h.

i flushed all the DNS entries with

dscacheutil -flushcache

(because lookupd is no longer available in leopard)

i checked by console my cache is empty with dscacheutil -cachedump giving me an empty status

strudel:~ alvarosoto$ dscacheutil -cachedump
DirectoryService Cache Overview:
AAAA Queries - Disabled (link-local IPv6 addresses)
Buckets Used - 0
Cache Size - 0

Entry count by category:

and then i changed my DNS to the opendns.org servers (208.67.222.222, 208.67.220.220)

The problem Persists /0_0\

for now the direct address option its fine but im guessing if the dsn problem comes from the operating system or by the ISP's

ill keep moving on

I don't know what is going on for you. I got that IP address doing a lookup (and I use OpenDNS's servers, so they should have looked-up the same for you as they did for me).

Out of interest, and in the vain hope that someone who actually knows what they are talking about might stumble by, what happens if you do a nslookup in a Terminal session on that LogMeIn server name? For example, it does this for me, which seems to be a correct and working result:

Ted-Harpers-iMac:~ tedharper$ nslookup secure.logmein.com
Server: 192.168.0.1
Address: 192.168.0.1#53

Non-authoritative answer:
secure.logmein.com canonical name = www.logmein.com.akadns.net.
Name: www.logmein.com.akadns.net
Address: 72.5.76.193

Ted-Harpers-iMac:~ tedharper$


(NB: The 192.168.0.1 address shown for the (DNS) server is my router, which is where the DNS settings for OpenDNS are configured; for a DNS lookup, my iMac asks the router, who then asks OpenDNS, etc).

I'm puzzled how, after flushing your DNS cache and changing to use the same DNS service as I am, you can end up with a different IP address being returned when looking up the same hostname, but puzzlement is all part of the fun, isn't it (sigh).


ted.h.

I have the exact same issue and it has to be an Apple/Leopard problem. My home network consists of a DSL connection (router) which then goes to an apple extreme router. I have an iMac and a Windows Vista machine connected to the apple router. The Vista machine can connect to the logmein.com website with no issue but my iMac just times out. The odd part is I have never used the iMac to connect to logmein.com until I tried today and it doesn't matter if I use Safari or Firefox.

I don't have the problem (my Macs are all on Tiger still). If you've tried the things above in the thread and they didn't help, someone suggested in another thread - they were on DSL as well - that you should decrease your MTU. From memory theirs was by default 1492 bytes and they reduced it to 1472 or thereabouts. Maybe something to do with LogMeIn.com's web server and fragmented packets? Anyway, maybe try a smaller MTU and see if that makes a difference for you.


ted.h.

Using https://72.5.76.193/home.asp?lang=en does solve the issue on my iMac but it still does not explain why it will not work when using httP://logmein.com. I don't see it being a DNS issue, afterall, it works fine on my Windows machine which is on the exact same network using the same DSL connection. This definately seems to be specific to Leopard. I took a look at the logmein forum and it sounds like a lot of Leopard users are having this issue.

What does a DNS lookup resolve secure.logmein.com as on your iMac vs on your Windows computer? That IP address is what it resolves as for me, but I'm in Australia and use OpenDNS for my DNS provide and it might be different for you.

Because accessing it via that particular IP address is working for your Mac, the problem probably has to end up being (1) secure.logmein.com is resolving to an incorrect or unreachable IP address for you, or (2) there is a configuration difference between different worldwide servers offering secure.logmein.com and it's luck/geography which decides which one you get (and whether that one happens to work with a Mac or not), or (3) something in the internet between your house and the particular secure.logmein.com server you are resolving to (which is different from the one I am getting to) is throwing away or mis-routing traffic from your Mac, but not your Windows PC.

So, to try to move forward on all of these, can you please post back what nslookup says the IP address is for secure.logmein.com from both your Mac and your Windows PC - I'll try the IP addresss your Mac wants to use from here (it has to be different from the one I resolve it as) and see what happens. Also if you didn't do so already, please try reducing the MTU on your Mac - System Preferences, Network, then select the adaptor you are using and it is on the Ethernet tab when you choose Advanced and Manual configuration (if it's 1500 now, try making it 1472).


ted.h.

Changing the MTU to 1472 worked for me
The problem is it is a temporary fix, it resets to 1500 after restarting my iMac
If anyone knows how to fix this permanently, instructions would be appreciated

Here's what i did

Open terminal and type or paste the following

sudo ifconfig en1 mtu 1472

enter you admin password when asked

close terminal and try to access logmein.com in safari