George:

        Heya. I think Matthew's and William's suggestion was spot-on:
you want to setup your firewall/router to forward the ports like this:

> ExternalIP:5900 -> Internal1:5900
> ExternalIP:5901 -> Internal2:5900
> ExternalIP:5902 -> Internal3:5900

        Then you only need to change the display number you're using
on the client side to be able to reach all of your machines.

        One possible downside: some low-end firewall/routers won't
allow you to remap a port-number like this (ie, sending 5902 external
to an 5900 internal). Most will nowadays, but I still comes across
networks where the appliance doesn't allow this. Another possible
hiccup is that if your internal network is using DHCP, your static
mappings in the router might not reach the machines your shooting for
if those IP address change. Again, with most of the newest router
appliances, DHCP is handled smarter than this so it won't be a problem.

        Another alternative you might want to try is Kaboodle. The
latest release version is 0.95, but I've got 0.99 working and it's
fairly stable if you'd like to alpha-site it. The idea with Kaboodle
is that it's a "VNC Gateway" and it uses only two TCP ports. So
if you've got Kaboodle running on PC1 on LAN1 and Kaboodle running
on PC2 on LAN2, you can VNC from PC1 to any of the VNC servers
which are a peer with PC2. Kaboodle uses Zebedee to create these
connections, so it has the added benefit of being a cryptographically
secured connection. Yes, you could use Zebedee (or SSH) on its own
to achieve the same effect, but I tried to take away some of the
hassle of getting all of the binaries playing together nicely.

        If you're interested in giving the pre-release version a whirl,
please let me know and I'll put a copy up on my server.

cheers,
Scott

> well, i have never done something like this, but it should work.
> each computer that you want to connect to only needs to have 2 ports
> forwarded to it, 580x & 590x (and you don't need the 580x one if you don't
> want to use the java browser). so, what you could do is at your router
> forward 5800 & 5900 to computer 1, 5801 & 5901 to computer 2, and so on.
>
> then when you want to connect to computer 1, you connect to your ip:0, or
> for computer 2 your ip:1. the :x means display number, and in essence is
> added to 5900, so yourip:1 connects to 5901 which is forwarded to computer
> 2.
>
> that should work. anybody know any different?
>
> ----- Original Message -----
> From: "George Hillman" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, October 15, 2002 8:52 AM
> Subject: 2 machines one external IP...
>
>
> > Greetings all!
> >
> > My issue is that I have 3 computers, 1 router which of course provides
> > internal IP's for my computers and connects to my real IP (actually I'm
> > using a DNS service to detect my ever changing DHCP assigned IP from my
> ISP
> > and map it to a world accessible host name).
> >
> > Now if I'm out on the internet away from home I can only reach one of the
> > machines because I cannot see the internal IP's for the individual
> > computers.
> >
> > So if I want to remote control any of the computers I have to set my
> router
> > to direct the VNC ports to one of the computers, connect to it with VNC
> from
> > outside the network, and launch the VNC viewer on the computer I connected
> > to. Now using the internal IP or network name I then VNC over to one of
> the
> > others. It gets slow and painful to do this!
> >
> > I tried setting different display numbers but that doesn't work... anyone
> > have such an arrangement where they can get at all the computers on their
> > network individually? What am I missing?
> >
> > George
> > _______________________________________________
> > VNC-List mailing list
> > [EMAIL PROTECTED]
> > http://www.realvnc.com/mailman/listinfo/vnc-list
>
> --__--__--
>
> Message: 7
> From: "William Hooper" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Subject: RE: 2 machines one external IP...
> Date: Tue, 15 Oct 2002 10:39:49 -0400
> Reply-To: [EMAIL PROTECTED]
>
> [snip]
>
> The basic concept is to take the external ports and forward them to the
> different IPs (which it appears you are doing).  So:
>
> ExternalIP:5900 -> Internal1:5900
> ExternalIP:5901 -> Internal2:5901
> ExternalIP:5902 -> Internal3:5902
>
> Depending on what you use for the sharing, it might be possible to leave
> all the display numbers on the internal machines the same, and just
> forward the ports appropriately.  Note you will still need a different
> display number in the viewer:
>
> ExternalIP:5900 -> Internal1:5900
> ExternalIP:5901 -> Internal2:5900
> ExternalIP:5902 -> Internal3:5900
>
> --
> William Hooper
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to