Remote Desktop Protocol

Forums › Desktop computing › Remote Desktop Protocol

SerjTank

42 posts

Geek
+1 received by user: 2

#41844 23-Sep-2009 22:44

So I've managed to get it working using tightVNC no worries, and viewing the remote computer via VNCviewer but I'd like to try and step it up a bit.

I've enabled port forwarding on the correct ports for tightVNC, yet my DNS still points to the router? This isn't so much a problem, but might be related to my other question:

is it possible to view and use RDP via an internet browser? This has obvious advantages such as being able to access my remote PC from pretty much any computer on the internet in the world. If I'm unable to do this I'll just get u3 tightVNC and use the VNC viewer from that...

Or is there a better (free) solution than tightVNC?

TIA.

War does not determine who is right. War determines who is left.

Ragnor

8279 posts

Uber Geek
+1 received by user: 585

Trusted

#257958 24-Sep-2009 00:06

Assuming you're talking about connecting to a windows computer...

1: Microsoft's Windows Remote Desktop Client would give better performance than TightVNC.

2: If the computer is running IIS (Microsoft's web server) or you can install it then you can install the Remote Desktop Web Connection and you will be able connect via a web browser on port 80 or whatever port you setup and forward to the box.

3: If you want to be able to connect from anywhere behind any firewall to your box that is behind a firewall you should use something like LogMeIn which negoaties or brokers connections.

rscole86

4999 posts

Uber Geek
+1 received by user: 462

Moderator

Trusted

Lifetime subscriber

#257970 24-Sep-2009 08:12

Do you want something like this?

http://www.uvnc.com/features/javaviewer.html

Kyanar

4089 posts

Uber Geek
+1 received by user: 1684

ID Verified

Trusted

#258342 25-Sep-2009 14:07

Remote Desktop Protocol and VNC are *not* the same thing. RDP is the native protocol used by Windows Remote Desktop (Terminal Services). VNC is an open source remote control client/server.

Anyway, whether you use VNC or RDP/TS, you'll need to forward both the RDP port or VNC port (3389 for MS TS, and 5900 for VNC) and whatever port your web server is on.

SerjTank

42 posts

Geek
+1 received by user: 2

#258355 25-Sep-2009 15:06

Thanks for the help so far, sorry for not mentioning it was to a XP machine.

Will try a few of the suggestions over the weekend.

War does not determine who is right. War determines who is left.

quandum

204 posts

Master Geek
+1 received by user: 5

#258463 26-Sep-2009 00:55

You will also need a static public IP, or dynamicDNS to rdp / vnc over the internet.

Have you tried teamviewer? www.teamviewer.com

I would love to change the world, but they won't give me the source code

#BOFH