If you use SSH....
LOCAL PORT: TARGET HOST(CAN BE A DIFF MACHINE ON THE NETWORK) : TARGET
HOST PORT
ssh -L 5555:localhost:5900 whoever@XXX.XXX.XXX.XXX
and then VNC to 127.0.0.01:5555 you can tunnel your VNC over ssh @ 256
bit encryption. That's what I do for RDP(port 3389) and VNC. I don't
like risking losing my logins and even with RDP 48bit encryption is
better than plain text but it's still kinda smelly.
If you REALLY want to get crazy throw a -C in there to turn on
compression and you should see better performance on a tight bandwidth
connection.
FYI: Change Halt at work today.... bored, heh ;-)
--Matthew Rogers
Eric Brace wrote:
>
> Basically the VNC relationship works in a viewer / server fashion. You
> install the server piece on a computer that you need to have remote
> access. You use the viewer on the computer you are going to use to
> connect to the remote pc. A few considerations, is the XP box behind a
> firewall? Does the XP box have its firewall on, if so you need to open
> the appropriate ports for the VNC apps to work. On the Ubuntu box you
> will need to install the viewer portion and make sure that if any
> firewalls are up on your side that the appropriate ports are open as well.
>
> RDP, can be enabled on XP by right clicking on my computer, selecting
> the remote tab and then checking off the allow users to remotely
> connect to this computer. Again make sure you punch a hole in any
> firewall for this port or protocol.
>
> Oh and one more thing to mention, if the PC is behind a router/switch,
> you will need to use port forwarding, I have actually seen smart cable
> modems too that have a port forwarding service in them also. Basically
> this tells the router to accept the connection and forward it to the
> appropriate IP / port on the other side. You basically have an outside
> interface with a public IP that needs to translate into your private,
> most likely 192.168.1.XXX:4600 address.
>
> Again, in Ubuntu I really like the Term Services / RDP client they
> built in, it really is smooth. VNC is cool to, but its flakey and can
> be a security concern, even moreso then RDP, but that’s another
> discussion altogether.
>
> Take Care!
>
> Eric Brace
>
> *From:* slug@nks.net [mailto:slug@nks.net] *On Behalf Of *William Coulter
> *Sent:* Friday, February 29, 2008 9:28 PM
> *To:* slug@nks.net
> *Subject:* Re: [SLUG] VNC question
>
> I have not been able to get RDP to work for me. I don't know or I
> can't figure out what I was doing wrong. I could give it a try again
> but I don't expect much from it by me.
>
> By going the VNC option, if I have tightvnc viewer on my PC, then how
> do I have control over the XP? (This is what I mean as I don't have a
> clue of what I am doing.)
>
> William
>
> On Fri, Feb 29, 2008 at 4:12 PM, Eric Brace <eric.brace@gmail.com
> <mailto:eric.brace@gmail.com>> wrote:
>
> You could use RDP, Ubuntu comes with a really nice TS clone for RDP.
>
> If your going to use the VNC option, install the UltraVNC server piece
> on the XP boxes and then install the tight VNC viewer on Ubuntu.
>
> On Fri, Feb 29, 2008 at 3:52 PM, William Coulter
> <wrcoulter33@gmail.com <mailto:wrcoulter33@gmail.com>> wrote:
>
> Ok, I have been reading from both web sites about ultravnc and
> tightvnc and I am not sure which one I should use. I don't do this
> in my daily work so this is strange and different to me. What I am
> trying to do remote control a family PC at another house. I run
> ubuntu linux but they all run XP. Both vnc's are cross plat form
> but why do some people use ultravnc over tightvnc and vice-a-versa?
>
> Thanks,
> William
>
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:16:27 EDT