webserver behind router?

Hi, I have setup my MN-500 router using a static IP, and
connected several desktop computers and a webserver to
it. I cant figure out how to configure the router to use
a different static IP address to access the server (which
is behind the firewall) to the "outside" world.

Does anyone have any suggestions? Virtual DMZ doesnt
really work because it doesnt map a static IP to an
internal IP. Can persistent port forwarding accomplish
this?... and how?

Thanks for any help or tips i can get!


shane

That's how I did it, with persistent or app triggered
port forwarding for port 80.

App triggered works fine with DHCP addresses on the LAN.
Persistent forwarding requires assigning a static LAN IP
to the server (a 192.168.2.x address) and then forward
port 80 to that IP. You choose.

People access the server using the public IP for the
router -- the IP from your ISP. (The router only supports
one IP from the ISP in router mode)

BTW, make sure that you have firmware 1.11.017 so
loopback is supported by the router, otherwise you cannot
reach the server using the public IP from machines within
the LAN -- which makes it trouble for testing.

>-----Original Message-----
>Hi, I have setup my MN-500 router using a static IP, and
>connected several desktop computers and a webserver to
>it. I cant figure out how to configure the router to use
>a different static IP address to access the server
(which
>is behind the firewall) to the "outside" world.
>
>Does anyone have any suggestions? Virtual DMZ doesnt
>really work because it doesnt map a static IP to an
>internal IP. Can persistent port forwarding accomplish
>this?... and how?
>
>Thanks for any help or tips i can get!
>.
>

What about the MN700, does it not have the loopback
enabled by default.. ?? ...
>-----Original Message-----
>That's how I did it, with persistent or app triggered
>port forwarding for port 80.
>
>App triggered works fine with DHCP addresses on the LAN.
>Persistent forwarding requires assigning a static LAN IP
>to the server (a 192.168.2.x address) and then forward
>port 80 to that IP. You choose.
>
>People access the server using the public IP for the
>router -- the IP from your ISP. (The router only
supports
>one IP from the ISP in router mode)
>
>BTW, make sure that you have firmware 1.11.017 so
>loopback is supported by the router, otherwise you
cannot
>reach the server using the public IP from machines
within
>the LAN -- which makes it trouble for testing.
>
>>-----Original Message-----
>>Hi, I have setup my MN-500 router using a static IP,
and
>>connected several desktop computers and a webserver to
>>it. I cant figure out how to configure the router to
use
>>a different static IP address to access the server
>(which
>>is behind the firewall) to the "outside" world.
>>
>>Does anyone have any suggestions? Virtual DMZ doesnt
>>really work because it doesnt map a static IP to an
>>internal IP. Can persistent port forwarding accomplish
>>this?... and how?
>>
>>Thanks for any help or tips i can get!
>>.
>>
>.
>

AHA! Updated the firmware and it works perfectly!
Thanks for the tips

>-----Original Message-----
>That's how I did it, with persistent or app triggered
>port forwarding for port 80.
>
>App triggered works fine with DHCP addresses on the LAN.
>Persistent forwarding requires assigning a static LAN IP
>to the server (a 192.168.2.x address) and then forward
>port 80 to that IP. You choose.
>
>People access the server using the public IP for the
>router -- the IP from your ISP. (The router only
supports
>one IP from the ISP in router mode)
>
>BTW, make sure that you have firmware 1.11.017 so
>loopback is supported by the router, otherwise you
cannot
>reach the server using the public IP from machines
within
>the LAN -- which makes it trouble for testing.
>
>>-----Original Message-----
>>Hi, I have setup my MN-500 router using a static IP,
and
>>connected several desktop computers and a webserver to
>>it. I cant figure out how to configure the router to
use
>>a different static IP address to access the server
>(which
>>is behind the firewall) to the "outside" world.
>>
>>Does anyone have any suggestions? Virtual DMZ doesnt
>>really work because it doesnt map a static IP to an
>>internal IP. Can persistent port forwarding accomplish
>>this?... and how?
>>
>>Thanks for any help or tips i can get!
>>.
>>
>.
>