If you would like to install manually, or do not use RPM to install packages, or have issues with the package manager install, try installing from source from the following link. Sun provides an RPM package at the link below. Most Linux distributions can install this from their Package Managers (RPM for Redhat based, Synaptic for Debian based, etc.). To use a Linux computer to control a Windows PC running LogMeIn, you will need to install the Java Runtime Environment. We do have official support for Linux on both sides of the connection planned for later this year, but for now, we do not support it officially. This is done through our legacy support for java, which is a cross-platform development environment. I recieved this message from a Logmein tech,Īlthough LogMeIn does not officially support the Linux platform, some Linux variants do support partial functionality to be used as a local computer controlling a LogMeIn target computer. (I am actually using this now to remote into my windows PC to post this so my work can't see where I've been :) The best though I can see is setup tightVNC or NX and hamachi on the linux box in question and simply tunnel using the hamachi IP of the linux box (see for all the details on mac/linux install) and it will resolve the issue of any IPs that change. Essentially it is for those of us that know of VPNs (or even those who don't) but want it to work easily and (from what I can tell) securely, oh and free. The reason I state this is that is allows a virtual 2nd nic (atleast under windows) and gets it so that all the computers setup under the client appear to be on one network.
It was bought out by and is available for linux/mac/windows and is free.
The method I use to get them to show locally to each other (without the more sophisticated VPN type setups) is called hamachi. One thing to remember is there are services for dynamic IPs (when your ISP changes it, this can be a hassle).
0 kommentar(er)
