Mark:
Heya. The part that is unclear is how you can connect
to Joe at all if your SOHO box doesn't allow port-forwarding.
My guess is that the SOHO has put Joe into the "DMZ", meaning
it forwards all ports, by default, to Joe. Not very secure,
but I'm sure it works.
Here are some ideas to get things working better:
1. Install an SSH server on Joe, and SSH clients on Mary and
Martha. You can then use SSH to setup a "reverse tunnel",
so that port 5901 on Joe actually connects to Mary, and
5902 connects to Martha, etc.
2. You can VNC to Joe, and then from Joe open a VNC Viewer and
connect to Mary or Martha.
3. You can replace your SOHO box with a $30 LinkSys box that
handles this much more nicely.
4. You can install Kaboodle on Joe, and then setup a "personal
VPN" connection to Joe from anywhere on the Internet. Once
connected, you can connect to Mary or Martha (Kaboodle uses
Zebedee to act like a connection-forwarding service).
Hope one of these helps!
-Scott
> Ok, let's hope this is clearer:
>
> I have a Windows2k Network with a single fileserver. Let's call it "Joe".
> This network shares a DSL connection to the internet, and we have a
> Watchguard SOHO Firewall. This network has (among others) two workstations.
> One is running WindowsXP-Pro, let's call that one "Mary". Another
> workstation is running Windows98SE, let's call that one "Martha".
>
> Right now, I can successfully run VNC Server on Joe, and from anywhere with
> an internet connection, use the VNC viewer to connect to Joe.
>
> I'd like to also run VNC Server on Mary and Martha, and, from anywhere with
> an internet connection, use VNC viewer to connect to Mary and Martha.
<snip>
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
