Howard:
Heya. Here's a more recent discussion about VNC and
NAT'ing firewall/routers like your DLink:
http://faq.gotomyvnc.com/fom-serve/cache/133.html
<snip>
> I have dug through the archives, but I must confess that I didn't
> understand a lot of what I saw there, especially concerning using VNC
> with NAT. The entries on NAT and VNC were all over a year old, too,
> so I'm hoping that there has been some additional progress made on
> that front. I have tried reading up on NAT, but I must confess that I
> didn't understand a lot of what I read on that subject, either.
>
> The work system is behind a firewall. My home computer is on a DLink
> 802.11b router, with an internal (192.168.0.x) address that can be
> either dynamically assigned by the router, or manually assigned on a
> router setup page. The DLink has a setup for something called a
> virtual server, with a list of internal IP addresses in the
> 192.168.0.x range next to dropdown boxes labelled "service" with the
> selections
>
> HTTP/SMTP/POP3/FTP/TELNET/IRC/ALL/NONE
<snip>
Some routers allow you to "port-forward" any port number
you want; it sounds like your DLink is only allowing you to
handle these 6 ports. Oh well. The easiest solution for you right
now is to choose "HTTP" for your "virtual service", and then setup
your VNC Server to run on port 80 (instead of its default port 5900).
Fortunately, this is very easy to do in version 4 of VNC.
Once your server is running and listening to port-80,
and your DLink is setup to "port forward" the external port-80
to your internal VNC Server, you should be able to connect with
a VNC Viewer from the outside world. Just be sure to tell it to
connect on port-80. Again, this is pretty easy to do in version
4 of the VNC Viewer.
Hope this helps!
cheers,
Scott
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
