[Eug]

At least I haven't been able to get LogMeIn to work, either with Safari (with the Mac plug-in) or with Firefox.



Worked fine in 10.4.10.

[ximon]

It still works for me using Leopard as the LogMeIn client, haven't tried the other way round yet but I assume you're referring to the client software since you mention Safari and Firefox...

[Eug]

Yes, with Leopard as the client.

Did you do an upgrade or a fresh install of OS X 10.5? I did a fresh install. It starts to work, as in I get to the login screen for the actual Windows XP PC I want to access, but after I log in I get a blank white screen.

[pumpkinpie]

I too have been unable to use Logmein on my PowerBook G4 to access my Dell. Both Safari and Firefox crash after second logon screen (which I assume has something to do with Java??). I did a clean install of Leopard. Any suggestions would be appreciated. BTW: I tested logmein access on another Mac which was a new intel iMac with a Leopard upgrade and it worked fine!

[sfmike64]

If you are attempting to use Safari on Leopard to remotely control other computers, just remove the LogMeIn plugin from the plugins directory (Library/Internet Plugins) and go with the pure Java solution. It's not as fast but it does work with leopard.

[Eug]

Thanks. I ended up reinstalling Leopard for other reasons anyway, so I no longer have the plug-in. I'll try the JAVA method. I just remember back in Tiger, I had problems with the JAVA interface with Safari 2. Firefox worked though... until I installed the Mac plug-in.

BTW, this should work fine on a G4 450 right? Right now my Cube is a G4 1.7, but I'm considering moving it over to work, and putting a G4 450 Cube in my home office. Most of my work is on a C2D iMac, but I have one desk which would strictly for LogMeIn and surfing.

[Eug]

Nope. Doesn't work properly in Leopard with Safari 3.0 with the Java client either. I can log in (which is more than before), but if I've gone to full screen mode, the screen will hang with a black screen when I try to disconnect.

I'll try Firefox without the Java client next. That worked for me in Tiger. (However, once you installed the Mac plug-in in Tiger, Firefox stopped working with LogMeIn.)

It will nice to get an updated Leopard-compatible Mac plug-in though, cuz it's the smoothest functioning of all the options.

[Eug]

Firefox is a no go too.

Both Firefox and Safari work in windowed mode (using the Java plug-in, without the plug-in), but if you go to full screen mode, you're stuck there. When you try to leave it, it just hangs at a black screen.

So in summary, with or without the plug-in, neither Firefox nor Safari work properly with Leopard. However, without the plug-in, both Firefox and Safari sort of work, as long as you never go to full screen mode.

[marcipano]

So, I think I've solved this...
Here's a screenshot of what I did (sorry, I'm using a russian interface, but the element positions are the same in english...)
mySkitch > marcipano > Picture 2

[Eug]

Java works, but not if you use full screen mode.

If I do use full screen mode with Java in Leopard, once I leave full screen mode I'm stuck with a black screen.

[Eug]

Warning: 10.4.11 updates Safari to 3.0. I haven't tried it yet, but I suspect that LogMeIn.com will no longer work right with Tiger's Safari 3 either.

[Eug]

So, it's now February 2008, and AFAIK they still haven't fixed it in Leopard.

[Andrew Stephens]

I'm on Lepard and it worked fine for me last night. Downloaded and instaled the latest release from the site and bam.

Being stoopid I forgot the password for my Dad's Mac (iBook 10.4) and got my ip locked out, so instead of waiting I logged into the mini in my office (Intel 10.5.1) and remotely controlled that to log into my dads iBook. All worked without a glitch.

[besson3c]

Is the draw towards LogMeIn the user friendliness or something? Just wondering, because you don't need a product like this to log in to your Mac remotely.

[Chuckit]

Yes, the draw is the fact that ordinary people without a CS degree can use it.

[mpancha]

I have it installed on my MBP (10.5) and my iBook (10.4) without problems. In Leopard, I downloaded the client and installed it, no hiccups here.

Also, connecting from either machine to another machine using logmein has worked fine in Safari and FF.

besson3c >> you can use VNC to log in remotely as the VNC protocol is built into OS X. However, you're assuming that the computer you are using to remotely access your own computer has VNC on it, and that if it doesn't, the owner of the computer is okay with you installing it.

The benefit of logmein for me as IT is that with it installed on end user machines, I can quickly assess their problems, and getting them to install the client on their end is dead simple. It works through routers, etc, with zero configuration.

For my own uses (testing sites, VPN connections, etc) It allows me to test things from a remote location, and check on tasks I may have running at home.

I still can not justify paying for .Mac, so logmein provides me the remote accessibility BackToMyMac does, with the added benefit of being cross platform, cross browser compatible. The only piece I don't get is remote spotlight searching, but if that's all I would gain for my $129, its not worth it. (I realize .Mac provides other things as well, but none of it is worth the cost for me personally).

[besson3c]

Utilities like Logmein, Back to my Mac, and even dyndns provide a useful service, no question... It will be interesting to see what will happen if one of these services is hacked. This seems like a big honey pot - particularly BtmM since it also authenticates. Does the Logmein server retain authentication credentials?

[mpancha]

They don't retain authentication information. It does prompt you to

1) login to your LogMeIn account
2) login to the computer you are accessing with its local credentials.

if the local account does not have a password, then you have to assign a password with the LogMeIn client running on the local machine which is then used to authenticate.

LogMeIn uses I believe 256-AES encryption, which allows me to worry a bit less. My general rule of thumb is if I'm using LogMeIn as a support tool (family/friends) I have them disable the LogMeIn client locally so no one can randomly access their computer. They only enable when I am taking control of the computer to fix an issue.

Granted, it may have its security holes, none of which I've experienced so far, but it suits my needs until something better comes along at least.

I'm curious as to what kind of encryption is used by BTMM

[Eug]

Is there anything faster out there, until LogMeIn fixes their Mac plug-in to work properly on Leopard?

I suppose I could learn how to set up a VPN and then run my Windows-only software (which is on my work PC) via Parallels, but that would be much more of a hassle, especially because the computer I normally access my work PC from is not an Intel Mac. (It's a G4.) That and the fact that I'd have to install the proprietary work software on my home computer without IT support.

Ideally, I'd be able to run LogMeIn with the dedicated Mac client, since it's much faster than without using the dedicated client. However, the dedicated Mac client simply doesn't work right in Leopard.

Now I'm considering finding an appropriate VNC server for the work PC and then installing the appropriate VNC client on my G4 Mac at home, but I won't bother unless it's faster than using the slow non-dedicated method of LogMeIn. Any recommendations?

[mpancha]

Eug >> what trouble are you having with it in Leopard? I've been using it successfully since my first install of Leopard when it was released. I also tried it on a couple computers at work, and it works there as well.

Your other option is to turn on Screen Sharing in system preferences on your Leopard machine, and from any other computer you can access the leopard machine using VNC.

In my findings, VNC is just painfully slow. It works, does its job, but LogMeIn has always been a good balance for me in speed and ease of use.

[besson3c]

I know this is not going to be the most popular thing to say, but learning some useful Terminal commands in many cases is much faster than LegMein or any of that stuff... I could have a file copied from machine to machine via scp probably before you could even get the LogMein page to load

[Chuckit]

Originally Posted by besson3c 

I know this is not going to be the most popular thing to say, but learning some useful Terminal commands in many cases is much faster than LegMein or any of that stuff... I could have a file copied from machine to machine via scp probably before you could even get the LogMein page to load

Perhaps, but could you teach somebody to set up DynDNS and configure their network to do it securely in less time than it takes to load the LogMeIn page? It seems less likely.

[Eug]

Originally Posted by mpancha 

Eug >> what trouble are you having with it in Leopard? I've been using it successfully since my first install of Leopard when it was released. I also tried it on a couple computers at work, and it works there as well.

The dedicated Mac client doesn't work properly in Leopard. I have tried it on 2 or 3 different Leopard Macs. I will try it yet again, but I note that people at the LogMeIn forums have the same complaint. The dedicated Mac client works perfectly in Tiger 10.4.10 with Safari 2, but chokes with Safari 3 in Leopard.

If I use the browsers without the dedicated Mac client, it works... but MUCH more slowly, and if I enter full-screen mode and then re-exit, it kills the link and I have to relaunch.

Your other option is to turn on Screen Sharing in system preferences on your Leopard machine, and from any other computer you can access the leopard machine using VNC.

I need to access a Windows PC. My Leopard computer is a client.

In my findings, VNC is just painfully slow. It works, does its job, but LogMeIn has always been a good balance for me in speed and ease of use.

The dedicated Mac-specific LogMeIn Tiger client dramatically speeded things up over their usual Java browser client. Furthermore, with it I can switch back and forth from full-screen mode at will without killing the link. This is useful if I'm doing multiple things on my Mac.

I'm tempted to just reinstall Tiger on this Mac, but have been holding out hope that LogMeIn would update the dedicated Mac client. Alternately, I could dust off that old P4 1.6 I have in the closet. << shudder >>

Originally Posted by besson3c 

I know this is not going to be the most popular thing to say, but learning some useful Terminal commands in many cases is much faster than LegMein or any of that stuff... I could have a file copied from machine to machine via scp probably before you could even get the LogMein page to load

I need to run commercial Windows-only software that is custom built for my workplace. It is a front end to access a large private database that is online 24/7 and is limited to my workplace.

So I have two options. Install the front end to that software on my home computer in Parallels Windows XP and access it via a VPN, or else use some sort of remote control option.

However, the VPN option doesn't really work, since the Mac I usually use for accessing my work computer is a G4 so I can't run Parallels on it.

[Eug]

Hopefully I don't draw too much ire for reviving this thread...

It is finally fixed! It no longer kills the browser when exiting full screen mode. Furthermore, the installed software applet works too.

I'm not sure why, but it may be due to the latest Java update.

[spitlizard]

I'm having the same problem but the other way around. When I try to connect to my Mac (OS X Leopard), logmein just sits there in the verifying screen though I know the U/N and password is right.

Anyone else had this problem?