Rasberry PI – VPN / Logmein Hamahi / Remote Desktop Connection via Windows [Solved]


juli 18, 2013 door Tim

I bought myself a Rasberry PI because I needed a remote desktop within another network, for configurating other routers and machinery. So I installed Rasberry with the default OS and set the desktop to boot automatically. Let’s see how we install Hamachi and the remote desktop you can use via the Windows Remote Desktop Connection.

First download and install Logmein Hamachi on your Rasberry PI

At first we need to update the packages because some of the packages needed may not be installed in your image.

sudo apt-get update

Install LSB (Required by Hamachi)

sudo apt-get install lsb lsb-core

Show some patience during the installation and download the latest Hamachi build for Linux afterwards.
Check for the right version the logmein page : https://secure.logmein.com/labs/#HamachiforLinux

sudo wget https://secure.logmein.com/labs/logmein-hamachi_2.1.0.101-1_armel.deb

Install the package

sudo dpkg -i –-force-depends –-force-architecture logmein-hamachi_2.1.0.101-1_armel.deb

First, connect your Raspberry Pi to your LogMeIn account and create a Hamachi network.

sudo hamachi login sudo hamachi attach [YOUR_LOGMEIN_EMAIL] sudo hamachi set-nick [NICKNAME_FOR_YOUR_PI]

On your client machines, go to LogMeIn and head over to “My Networks”. If everything went well you should see your Raspberry Pi trying to connect and create a new network. Give the Pi the right to create the network and note the 9-digit network ID.

Back on your Raspberry Pi enter:

sudo hamachi do-join [NETWORK_ID]

You might be asked for your LogMeIn password and approve the requested access to the network on the client. After this step the Pi is part of the Hamachi VPN. Look for the Pi’s IP-address in the VPN at LogMeIn and remember it.

Start the SSH Server to connect and control your Pi remotely.

sudo /etc/init.d/ssh start

And finally set the hamachi to autostart with Rasberry PI when (re)booting

sudo update-rc.d logmein-hamachi enable

Install the Remote Desktop Connection on your Rasberry PI

  1. Start up your Pi to the terminal prompt.
  2. Type the following command
    sudo apt-get install xrdp
  3. If promoted enter your password (the default is “raspberry”) otherwise it’s your own chosen password
  4. Type “Y” and press enter.
  5. This is now installing xrdp onto your Pi which is the software we are going to use for the remote desktop connection.  Wait for it to complete.
  6. Restart your Pi.  We are going to check that xrdp is going to start up automatically.
  7. When your Pi has booted to the command prompt look for [ ok ] Starting Remote Desktop Protocol server : xrdp sesman.  This shows you that xrdp is installed and automatically starting up on start up of your Pi
  8. The last step is to make a note of the IP address of your Pi which should also be displayed on the start up screen.  In my case below it is  This is the address of your Pi on your network and what we will use to connect to your Pi from the second machine.

Second Machine Setup

1. Launch Remote Desktop Connection which can be found at Start->All Programs->Accessories->Remote Desktop Connection
2. Type in the IP Address for your Pi which you noted above.
3. Click Connect (you may get a security warning at this stage just click OK if you do.  After all it is your Pi on your network so nothing to worry about security wise).
4. Leave the Module on the default of sesman-Xvnc and enter your username and password for your Pi.  (The default is pi and raspberry if you haven’t changed them).
5. Click OK and after a few moments you should be greeted my your Raspberry Pi’s desktop!

3 thoughts on “Rasberry PI – VPN / Logmein Hamahi / Remote Desktop Connection via Windows [Solved]

  1. Tarab schreef:

    great tutorial!
    So, I have a question: the ip you mentioned in article is a local ip.
    Can I access to my raspberry remote desktop via hamachi if I am on a different network?

  2. Dude schreef:

    First, thanks for this very usefull tutorial. It saved my quite some time.
    I just wanted to point a little detail out.
    The first dash in “–-force-depends” and “–-force-architecture” is not a standart dash character. So if you copy/past the command in a shell, it will ignore the first dash, ending with “-force-depends” and thus throwing an error.

  3. Tim schreef:

    Thanks for clearing that out :-)!

Geef een reactie

Vul je gegevens in of klik op een icoon om in te loggen.

WordPress.com logo

Je reageert onder je WordPress.com account. Log uit /  Bijwerken )

Google photo

Je reageert onder je Google account. Log uit /  Bijwerken )


Je reageert onder je Twitter account. Log uit /  Bijwerken )

Facebook foto

Je reageert onder je Facebook account. Log uit /  Bijwerken )

Verbinden met %s

Deze site gebruikt Akismet om spam te bestrijden. Ontdek hoe de data van je reactie verwerkt wordt.


juli 2013

Blog Stats

  • 228.380 hits
%d bloggers liken dit: