vnc router issue
cenvnc "at" gmail.com
Mon Apr 4 16:14:01 2005
First of all thank you both for the replies. This is my first time
using this mailing list and to find 2 excellent replies on my first go
is excellent luck.
well ive tried this command on a linux client
'vncserver -connect 80.**.**.**'
but the -connect switch is not recognised. I'm on version 4.0 of vnc
But you have hit the nail on the head. It is *this* type of passive
connection, i believe would be best suited to the problem stated.
On Apr 4, 2005 1:27 PM, Angelo Sarto <angelosarto "at" gmail.com> wrote:
> The vncserver has a command line option called "-connect" that, in
> short, initiates a reverse connection. That is, it connects from the
> server to the viewer (default port for this is 5500, I believe).
> If your viewer is always at a certain IP (or domain using a dynamic
> dns entry) then you only need to have 1 port forward per client
> instead of one per server. (This port forward needs to be installe
> don the client side router/NAT/PAT device.
> The only limitation to this is that the server machine must initiate
> the connection, which is fine if the user is present. If you want
> access even when the user is not present then you can try something
> like the following:
> 1. set up a cron job that checks *some* directory for a specific file.
> 2. If the file is present initiate a reverse connect, else exit the job.
> 3. Now, the only thing left is to figure out where and how to get
> that file in place, and for that you would have lots of options, SFTP,
> HTTPS, or even telnet access to any machine that can create said file.
> Good Luck,
> On Apr 4, 2005 5:43 AM, hokage hokage <cenvnc "at" gmail.com> wrote:
> > Hello,
> > Am a new convert to this unix lark! just recompiled me first kernel
> > and installed x.orgs latest version, like two days ago. So as u can
> > see i am *total freshie*. Have come across a problem.
> > I work for a company that carries out support.
> > We are supporting a company that has around ten client computers and 1
> > server, all on internal 192.168.*.* addresses.
> > These computers are only accessible through a router. There static WAN
> > address provided by there isp forwards all traffic to the router.
> > Whenever there is a problem on a specific client, i would like that
> > client to initiate a program that allowed me (i am on a completely
> > different network) to *access that particular* client.
> > *i really do not want to use port forwarding because we want 2 handle
> > clients that have 100 or more terminals.* Specifying 100 ports on a
> > router fills me with horror.
> > I'm sure there is a standard tried and tested way of doing this, but i
> > cant find it. Even using the search func provided by the forum. *Any*
> > help on would be much appreciated.
> > _______________________________________________
> > VNC-List mailing list
> > VNC-List "at" realvnc.com
> > To remove yourself from the list visit:
> > http://www.realvnc.com/mailman/listinfo/vnc-list