On Friday 02 December 2005 21:49, Marc Chamberlin wrote:
I am running a small network of various computers and want to be able to configure each of them so that I can administer them remotely via remote desktop (aka VNC) The way I have been doing this is to assign each computer its own port for its server to listen on, so Comp A is listening on 5900, Comp B is listening on 5901, etc. I use the SuSE Control Center to configure the remote desktop server on each computer, and start the server via the inetd daemon. I have configured my SuSE firewall computer to route incoming requests to the appropriate computer. In the past all this has worked fine.
<snip>
Marc.....
Yo Marc. I have several networks similar to the ones you described. I use a different method to get to the workstations though. Since I think my method is better I'll explain it to you. 1) I leave all the workstations on 5900. (Less hassle that way). 2) I allow ssh into the SUSE server/firewall 3) from the other side of the world (well from Switzerland to Houston), I Issue the following command on my linux laptop: vncviewer -via mybrothers.office.com WS01 The -via command is a tightvnc extension (tightvnc is default vnc version on SUSE). It tells vncviewer to start an ssh tunnel to mybrothers.office.com (The SUSE firewall/server), and from there to forward the connection to WS01. This method has the following advantages: - only need to open ssh on firewall. - no need to remember portno - host associations - needs no additional configuration on workstations - works for windows workstations also. Jerry