> -----Message d'origine-----
> De : Seak, Teng-Fong
> Envoyi : lundi 9 fivrier 2004 14:00
> @ : [EMAIL PROTECTED]
> Objet : RE: VNC behind Watchguard SOHO
>
> > -----Message d'origine-----
> > De : Mark [mailto:[EMAIL PROTECTED]
> > Envoyi : vendredi 6 fivrier 2004 18:44
> > @ : [EMAIL PROTECTED]
> > Objet : RE: VNC behind Watchguard SOHO
> >
> > I re-read the VNC FAQ about 8 times, followed by re-reading the SOHO manual
> > about 4 times. The SOHO allows custom services that listen for incoming
> > traffic on certain ports and redirects it to an internal IP address. That
> > sure sounds like port-forwarding to me, although they don't call it that AND
> > it is also stated that the SOHO units don't allow port-forwarding.
>
> It can be called "virtual server", "port mapping" or even "PAT" (though this
> isn't
> exactly the same as port forwarding).
You've never precised which model you've using, so I just did a google search
on "watchguard soho", go to the first match, click on "security features" and there, I
can already see the word, "NAT" ! I then clicked on it which gets to this
http://www.watchguard.com/products/addtran.asp?nav=fbs
There, at first glance, I could already spot several keywords we're using:
NAT, SMTP "Port forwarding". It's unusual that such new device wouldn't support port
forwarding or any minimum functionalities that most router do nowadays.
> > So, I was able to make it work by:
> >
> > I. Setting up multiple custom services on the SOHO - one for each
> > workstation I want to access. For example 5900 is redirected to the
> > fileserver, 5901 is redirected to Workstation #1, and 5902 is redirected to
> > Workstation #2.
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
