At 12:19 PM 2/18/2001 -0800, you wrote:
>Eric,
>
>As a user of the LinkSys box, this is sounding fishy. Are you, by any
>chance, using the DHCP server of the firewall?
Nope, static IP's all around (internally).
> Have you updated to the
>latest firmware?
Yes, running 1.37 dated Jan. 3, 2001.
Eric,
As a user of the LinkSys box, this is sounding fishy. Are you, by any
chance, using the DHCP server of the firewall? Have you updated to the
latest firmware? Used to be that certain port forwarding or filtering
features wouldn't work if you were using the DHCP server (don't ask me why).
Cou
At 11:41 PM 2/16/2001 -0800, you wrote:
>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 *fo
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
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 ha
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
