Download Logmein Client
Ilia Zable
When you what to access your work computer you connect to the logmein server. The server then tells the client software on your work computer that you want to connect and the client establishes a connection between your home computer->logmein server->work computer.
Previously up to Firefox v.25 there was a LogmeIn extension, which stopped working in v.26. I removed that, but Firefox behaves as if I still have an appropriate extension, and never offers the install of a new one as per the logmein document just mentioned.
Thank you for your advice. On starting the LogMeIn process, there was unfortunately no change, and the push download appeared, was installed but would not start - just as before. I do have a logmein app in the firefox setup config now, that describes it as an app, so that is a step forward.
It is named logmein client.exe and now I know why it 'does not start' - it is because I have win 7 pro, which enabled me to set a group policy preventing execution of anything in appdata\local except what I allow. As soon as I managed to rediscover how I did that (!!) and allowed logmein client.exe, the app now works.
After much testing and trying, I figured out what the problem is. The logmein client installs itself with a cookie. Very important. My FF was set up to delete cookies upon exit. When I leave the cookies alive for the next session, it doesn't require the reinstalling of the logmein client.
About IE11 and Firefox etc, my IT assistant has found this for me -management/logmein-impending-death-browser-plugins If you want a good laugh, read the dozens of highly critical customer posts that are on there. LMI has shot both feet, but is blaming Firefox.
So through Continuum it only gives the web interface. There is no option through them to have the actual application of Logmein. It downloads an individual client for every computer in the system. So it downloads individual sessions each time with different URL's.
I'm thinking it may be due to the way the DNS is resolving. I've also got a number of other LogMeIn FQDN objects that LMI uses (logme.in, etc), but I'm focusing on logmein.com as the above settings should be allowing it. I do not have any UTM features such as Application or Web filtering enabled at this time. There is only 1 host on the lan interface, and it's getting IP/DNS settings from the firewall.
Wildcard entries are not allowed for FQDN address labels. Since it's port 80/443 traffic, you may have better luck crafting a wildcard url filter for *.logmein.com -- add that to your main web filter profile (that's is covering your main web traffic policy). Set the url filter to allow.
Result is the same, no connectivity and all traffic to logmein.com is being denied. The log and debug outputs show that the traffic is failing the policy check, which to me means that the traffic is not matching the rule. I just can't see what could be wrong with the rule in question.
I'm thinking that the LogMeIn client software on the test host is trying to connect using an IP rather than FQDN. Would this cause the traffic to fail the policy check, despite the IP being assigned to the logmein.com domain?
Personally, I'd would use a wildcard url filter (not FortiGuard web services) for what you are trying to accomplish. Since your dilldown log shows the client trying to connect via HTTP/HTTPS, I don't see how it wouldn't work. (Of course, I am assuming actual web traffic and not a port 80/443 data "tunnel".)
Regarding IP lookups for FQDN addresses -- I too was wondering about this since most of our clients are in remote areas with very slow satellite linkups. Never found an actual official answer (of course I merely did a curiously check). I just ended up playing around with the cache-ttl values (from the CLI) for key FQDNs.
FQDN Firewall Address Object simply looks up the FQDN and substitutes the IPs as the object. Any time a client gets a different IP back it will fall outside the policy. Any time the client tries to go to one of the other many addresses owned by servers used by facebook or youtube, that don't fall within the IPs resolved by www.facebook.com, it will fall outside the policy. FQDN address objects are NOT intended as a webfilter and you cannot specify *.facebook.com as an FQDN Address object. How do you do an nslookup for that? Answer is you can't.
If you choose I will send the invitation myself, you can click Copy link to clipboard and then paste the link in an email. Also, you can click Use in a new message with my email client to open your email and send a pre-written message. Then click Finish.
I have to manage some windows server by logmein. But I use ubuntu as client... looks that logmein does not work under linux... it's the same for you ?Simply I connect to logmein, I authenticate myself, try to connect.. java giveme some errors..
Under Security Appliance>Firewall we had a Layer 7 firewall rule setup to Deny P2P - BitTorrent. This rule was blocking any Logmein traffic coming from the outside and was resulting in disconnection issues from the Logmein client. When I removed the Layer 7 firewall rule above the issue subsided. Figured I'd give everyone a heads up and I'd also be interested in any dialog regarding effective prevention of P2P traffic on your networks. Seems like the current Layer 7 implementation blocks a lot of legitimate traffic.
The free client is available for PCs and Macs, and offers a very simple suite of remote desktop control features. It's worth noting that the key word here is "control". When you log into a remote computer with LogMeIn, you'll assume control of it, with a small dialog appearing in the top right-hand corner of the remote PC's screen informing them that you're at work. If you don't see that pop-up window, assume something bad's happening to your system.
The Pro client offers the same remote control facility with the added features of remote printing, remote file transfer via drag and drop, drive mapping, remote sound and file synchronisation. The interesting catch here is that while the free client is available for Mac and Windows computers, Pro is to date a Windows-only option.
As noted, the paid Pro version offers a lot of additional functions such as file copying, remote printing and remote sound, but these are Windows-only functions on both the client and server side. We could access a Windows machine with a Pro account from a Mac, but not stream sound, for example. Our attempts to get the LogMeIn client to run on a Windows 7 RC1 were met with a brick wall of installation failures, and online research didn't help much with a variety of fixes that we couldn't get working. With the strong Windows focus of the application, hopefully that's something that will be rectified shortly.
The other obvious use for LogMeIn would be in the oft-dreaded case of being your family's technical support. While most operating systems have had remote client sharing as a feature for some time, there's few that operate as seamlessly as LogMeIn, and it'd certainly beat a 30-minute phone call while you try to get grandma just to click on the start button. Not that we're speaking from experience, or anything.
On the iPhone side of things, the client works quite well, with options to drop the screen resolution and colour depth on a temporary basis to improve overall speed. Pinching and zooming around the screen works well. There's no sound support, and our tests with video left us with large black boxes where video should be.
LogMeIn does admittedly sell itself predominantly to the aforementioned business crowd, and given the lighter needs of the consumer-led audience a mix of the iPhone client (where needed) and the free client are arguably sufficient.
LogMeIn Hamachi for Linux is a secure VPN client for Linux that offers connectivity to your resources from dispersed environments. Unlike Hamachi for Windows/Mac, the Linux client uses the command line and offers a relatively limited set of features. For details, check the Hamachi User Guide.
We're interested in your feedback. Once you've tried the client, please let us know about your experience at hamachi-...@logmein.com. Your feedback will help define the priorities of further development of the product.
In addition to building a secure gateway between the client and host computer, LogMeIn provides two further layers of security: TLS and LogMeIn Intrusion Filters. TLS (transport layer security) provides its own two checks to ensure your data has not changed in transit: record sequence numbering and message authentication codes. Mismatching keys means your data has been tampered with, and the transfer will fail. The LogMeIn Intrusion Filter has three components: IP address, denial of service, and authentication. These three filters ensure that bad actors are not connecting through an unknown IP address, hitting your site with an excessive number of connect requests, or trying to guess passwords through a high number of random tests. Each of these acts are common hacking techniques that LogMeIn guards against.
GoToMyPC similarly guards against denial of service attacks and excessive password tries through server monitoring. In addition, firewalls are deployed between the servers and the connected host or client computers. Because users can access the GoToMyPC servers from any web browser, search history is a security concern that the company has planned for. Although the program will show up as GoToMyPC in search history and may download an optional cookie to the computer, neither of these leave behind any identifying information or specific histories that could endanger the security of the data.
df19127ead