Pan said:
i find simple. rdesktop works out the best. but if u insist on going vnc way, have a look at TightVNC. Its secure.
Actaully, if you added some SSH tunnelling it would approach security .. then again just because the 1 tunnel is secure it by no means anything else on the pc is ;-) ... sorry just being full of ****e
As to a suggested solution:
There has been some suggested advice already given which you certainly can go with. I'll add my 2cents worth in the hope that it saves you some trouble.
If you're looking for a cheap/free solution you're going to have to plug-'n-play a little bit (not a lot mind you). There are also some commercial remote desktop options that I can recommend if you need.
So, enough rambling and onto the free solution:
1) Get a dyndns account at
www.dyndns.org (free for <5 hosts)
2) Register a host
https://www.dyndns.org/services/dns/dyndns/
3) Get a dyndns client running...
Windows:
https://www.dyndns.org/download/clients/windows/dyndns-setup.zip
Linux: ddclient.sourceforge.net
Configure them to use the hostname you registered in step 2 (RTFM).
At this point you'll be able to GET to your box ...not access it yet.
If you're using Microsoft's built in Remote Desktop (see MS Help to run it) you need to remember that port 3389 (tcp) needs to be opened on the firewall.
If you're using vnc (most derivatives) default port required is 5900 (as mentioned above
http://www.tightvnc.com is a good option - RTFM there to get it running [make SURE to let it run as a service])
You need to now open up the above mentioned ports on the firewall you have installed (you hopefuly are using SOME firewall).
If you've managed all the above and didn't need a drink break ... congratz....
You should now be able to use either the Remote Desktop client or the VNC Viewer to access your box via the dyndns domain name ...
If all this is GREEK to you, PM me and I'll see how I can help.
R