I am using VNC on different "displays", so that it uses different ports to
listen on (5900, 5901, 5902). Then I forward those ports on the NAT box to
the internal IP address that they go to. Technically, you could "remap" the
ports, so that each internal machine is using the default (5900) and the
port-mappings on the external IP map to them (5900->5900 on machine one,
5901->5900 on machine two, etc.) I did it like that once for a job.
But I'd rather just have the internal machines set to use different (from
the default) displays, so that each internal machine is always accessed on
the same display (i.e. port) whether from in the inside or outside.
(Granted, from the outside, they all appear to have the same IP address, but
that should be understood).
It helps to prevent problems like, "I know i want to get to Snoopy, but I
forget which port is mapped to that from the outside." If you always have
to use snoopy:9 to get to it, then you will remember to use nat-box:9 to get
to it from the outside.
Jordan
----- Original Message -----
From: "Joseph A. Knapka" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 05, 2001 1:31 PM
Subject: Re: Single Port File transfer
> As for the one-to-many NAT problem, that is tricky, but obviously
> you have done something to allow VNC connections in this situation
> (how do you handle that, by the way?), so do the same thing for the
> ftp port that you do for the VNC one and you should be on your way.
>
> -- Joe Knapka
---------------------------------------------------------------------
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
---------------------------------------------------------------------
