-Set up an SSH server (CopSSH) customized to run on port 443
-Open the port 443 on the router to point to my server's LAN IP (ie: 192.168.1.101)
-(Optional) Set up a DynDNS account and install the DynDNS client to have an hostname (ie: mybox.dyndns.org) associated to the WAN IP (ie: 200.41.78.47) to make sure to can connect if the WAN IP change
-Set PuTTY to connect to the server (ie: mybox.dyndns.org:443)
-Set up an SSH tunnel for a loopback connection of the local Remote Desktop port (ie: 3390, can be something else) to be redirected to the Remote Desktop port (3389).
Source port: 3390
Destination: localhost:3389
Local, Auto
Once connected, connect to localhost:3390 in Remote Desktop. All the traffic will be tunneled through the SSH connection to the remote server, which will listen on port 3389 without opening additional ports, reducing the possibility of traffic sniffing and attacks.
Hi
You can try showmypc
www.showmypc.com
IT specialist
Writing/book coach
Ghostwriter
Game creator
I am using team viewer , there is also a portable version on their website.
Otto Sykora
Basel, Switzerland
I use a secured SSH connection, in which I tunnel a RemoteDesktop connection from XP Pro.
can you more in depth in what you did. and what features you get.
TeamViewer is the best remote desktop manager it's free and always works
-Set up an SSH server (CopSSH) customized to run on port 443
-Open the port 443 on the router to point to my server's LAN IP (ie: 192.168.1.101)
-(Optional) Set up a DynDNS account and install the DynDNS client to have an hostname (ie: mybox.dyndns.org) associated to the WAN IP (ie: 200.41.78.47) to make sure to can connect if the WAN IP change
-Set PuTTY to connect to the server (ie: mybox.dyndns.org:443)
-Set up an SSH tunnel for a loopback connection of the local Remote Desktop port (ie: 3390, can be something else) to be redirected to the Remote Desktop port (3389).
Source port: 3390
Destination: localhost:3389
Local, Auto
Once connected, connect to localhost:3390 in Remote Desktop. All the traffic will be tunneled through the SSH connection to the remote server, which will listen on port 3389 without opening additional ports, reducing the possibility of traffic sniffing and attacks.