NOTE: IT WILL WORK BEHIND ROUTERS :D !!!
DISCLAIMER: I AM NOT RESPOSIBLE FOR ANY DAMAGE INCURED TO YOU, YOUR COMPUTER, YOUR FRIENDS / ENEMIES COMPUTER AND ALSO BUT NOT LIMITED TO THE SAFETY OF HUMAN KIND. IF YOU INTEND TO USE THE CONTENTS OF THIS TUTORIAL FOR ANYTHING AGAINST THIS DISCLAIMER DON'T CONTINUE TO THE NEXT STEP.
Remove these ads by
Signing UpStep 1Things You Will Need
- A computer
- Internet - preferably fast but any will do
- A flash drive or other means of mass storage devices.
- Windows Live Messenger with sharing folders enabled and two email addresses
- Time
Hamachi Setup files - https://secure.logmein.com/products/hamachi/download.asp
Hamachi - Buri - Buriproject.info (Download)
TightVNC - http://www.tightvnc.com/download.html
TightVNC Portable - http://portableapps.com/node/11285
| « Previous Step | Download PDFView All Steps | Next Step » |









































The Instructable doesn't really explain how Hamachi comes into play. Standard VNC connections are unencrypted, so snoopers can easily find your VNC password. If you need the connection to be secure you normally have to tunnel the VNC connection through SSH. Hamachi will make a secure VPN running on their servers that's connected to your computer, acting like a tunnel. It's like a reverse connection on both sides being joined together by the Hamachi server. This makes it both easy to connect (it logs in to their web address instead of you having to find your IP) and secure (anybody trying to break Hamachi security is probably insane).
Without Hamachi:
For finding you server's IP it's easy to use stuff like No-IP (or Afraid.Org for more advanced user) to create a static-IP (a web-address that is synced to whatever IP you are currently using). Or you could do the opposite and do a reverse-connection by sending VNC (server) connection requests via batch, which would connect once you update the static-IP and run VNC client in listening mode. Most modern "remote administration tools" are already made for reverse-connections, so all you need to do is update your static-IP and run the client.
And I like that last optional thing. I would love to have something like that. It would be great on smart-phones like a Droid or iPhone or Nexus One. You could call up, turn on the computer, and then turn on the VNC.
Tunneling through SSH would be a much better solution. It's secure, more reliable and there are no third parties to monitor your traffic. (Not to say I'm ungrateful for hamachi, they're a wonderful organization)
As OpenSSH is a native Unix application, tunneling a windows-based VNC server through SSH is somewhat of a challenge. If I encounter a lazy weekend in the near future, I might write an Ible on setting up an OpenSSH server on windows (using Cygwin) and using it to tunnel a VNC connection.
Cheers,
Eages.
p.s. Belated replies lol.
Do you still know the steps ? And could you please tell us these steps ?
Thanks mate
I haven't looked at this instructable in years and can't remember how to pack the buri files. However, I do remember you do most of the transferring during setup. As stated here: http://logmeinwiki.com/wiki/Hamachi:Buri#Download_Locations There should be text files in the buri directories to help you through the process. Please be advised that this method of connecting to your computer is quite redundant.
As a preferred alternative, you might like to look into installing 'TigerVNC' and forwarding the appropriate ports on your router. I believe it is possible to encrypt the traffic using that program too.
I'm thinking that I'll eventually make a new ible with instructions on creating a VNC server and perhaps tunneling it through SSH.
Regards,
Eages.
my pc was already set as a Apache server but had a Dynamic IP so i installed an IP updater that connects a zapto domain (or other). to my IP. Then i just had to extract the zip of the viewer into my usb (along to make it fancy with the portableapps menu).
Pro: Only have to boot VNCviewer (fast)
Contra: If you not use port 80 for Http (apache) traffic the site of the updater (No-IP.com) considers the domain as idle and sends a mail with a link to extend the duration every 14 days.
The new URL is: http://www.buriproject.rd.to/howto/ .
Regards,
EaglesNestOne
- You are not an Administrator (you're using a limited user account);
- Your system firewall may be blocking hamachi;
- At least one of the two computers in question is not properly connected to the internet (unlikely);
- Alias's need to be set. And using hamachi Alias's calls for a whole seperate instructable...
If you still have problems after doing this feel free to post back your system specs etc. and I'll see what I can do.I hope this helps,
EaglesNestOne
EDIT: Also, using the Internet Browser method isn't necessarily totally portable, as Cookies etc may be left on the client computer. With this method, all traces are deleted when hamachi is closed. Leaving the client's pc clean.