Accessing a server behind a firewall

[James "Wez" Weatherall]

> The problems with this are:
> Every time the scheduled task runs, it pops up a new window. If I try to
set the server to only use DISPLAY 0, the connections seem to be queued. If
I kill  one, the next one pops up straight away. If this goes on for long
enough, without me cycling through queued pending connections, the server
appears to freeze. I am using WIN98 at both ends.

Add New Client adds a new client - it doesn't kill old ones.  The freeze
could well be a deadlock I've recently found but I suspect it's just because
you're ending up with loads of concurrent connections to a single server.  A
deadlock-free version will be available very soon.

>
> Is there anyway I can trigger the server PC to initiate a VNC session on
demand, instead of on a regular basis?

The easiest way is to SSH into the machine in question and run
"winvnc -connect" in the telnet window.  You can get an SSH server for
Windows that works fine for this purpose.  If you're allow HTTP access then
an easier method might be to have a server which remotes the display to a
fixed machine (your PC) whenever a GET or POST message arrives for a
particular page.

Cheers,

James "Wez" Weatherall
--
          "Xenophobes should go back to Xenophobia"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK                              - Tel : 343000
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------