Eric:
Two quick questions for ya:
1. Have you ever gotten the LinkSys box to forward any ports?
I mean, not just for VNC, for anything. Sometimes you have
to specify *opening* the port, as well as specifiying that
you want to *forward* it; two-steps.
2. Next time you've got the port-forwarding setup for your
VNC box, try connecting to it with telnet. So, telnet to
209.172.152.101:5900 and report how it fails. It if drops
quickly, the firewall is likely still blocking the port.
If it lingers...it may be that your LAN machine is having
difficulty getting packets *out* of the firewall.
Good luck!
-Scott
PS: Alternative: get a firewall with a *lot* more support -- see
leaf.sourceforge.net. Great project. :)
> Thanks Lyle. That is exactly how it works for me now. With the DMZ host
> turned on ALL ports automatically get forwarded to my private IP from the
> router. What I am trying to do is to just forward the ports needed for VNC
> and turn off the DMZ feature leaving the rest of my ports secure.
>
> I have tried every range of ports I can think of (and read about thus far)
> and none seem to work.
>
> At 09:11 PM 2/16/2001 -0600, you wrote:
> >The only issue I can think of right off hand is that you have to connect to
> >the public IP address of the router. For instance, your router has a
> >public(Internet) address of 209.172.152.101 and your internal machine is
> >192.168.0.50. Then you would try to VNC to 209.172.152.101:5900 (or :5800
> >from a browser). And the router should be forwarding ports 5800 & 5900 to
> >192.168.0.50.
---------------------------------------------------------------------
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
---------------------------------------------------------------------
