I have used VNC for a while now in our internal network, and find it very
useful. We are now thinking about using it over longer distances (i.e.,
over the internet) to control software on some of our customers' machines.
We can put pretty much whatever software we want on the end-user machines
(almost certainly NT 4.0, possible win2k), but we cannot change how these
are connected to the outside world. If they have a dial-up connection,
things are easy - they get a temporary IP address from their ISP, and either
tell us it via another telephone line, or we can make a quick program to
find out their IP address after dial-up and send it automatically to us.
However, if the target machine is connected to the internet via an network,
with a firewall and IP masquerading, things are going to be much more
difficult. We cannot tell in advance if they have a unix box, and NT
machine, or a stand-alone router/firewall, and we cannot really insist that
the end user changes his router/firewall setup. For example, in our network
here we have a stand-alone router with network address translation, so my
machine has an IP address of 192.168.0.34 (or similar), and is invisible
from the outside. The dial-up router is fairly simple, and cannot be given
complex forwarding rules. Is there any way that I could make a VNC server
on my machine accessible from the outside?
Thanks for any help.
David Brown
System Developer
WestControl a.s
Norway
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
