Access to static WAN IP on LAN

[rhsherman]

I'm relatively new to routers. I'm trying to figure out how to gain access within our LAN to our web server through the ISP WAN static IP (we don't want to use the local static web server IP address of 192.168.1.3). When I called tech support they told me that I must configure the web server (IIS 6) to map the static WAN IP address. I'm not exactly sure what that means... Before installing the NETGEAR FVS318v3 firewall router I had a competitor’s router that didn't have this issue, thus my confusion. The router is a FVS318v3 Firewall Router, firmware v3.0_26RC1, which is connected to a cable modem. I'm able to access the web server fine outside of LAN. Any help would be appreciated.

[jmizoguchi]

you should able to loop back to your web server using WAN IP

I know old FVS318V24 I have at all my clients works fine.. I never check on V3 but here is some to read

http://www.dyndns.com/support/kb/loo...nnections.html

[rhsherman]

June, thanks for the link. This worked great! The only drawback is having to go around and update all the computer's host file in our office, but I'm willing to live with that. Thanks again for the help.

[jmizoguchi]

glad it worked for you... !

[vicente]

Hi,
I read the article referenced by Jun and found it very confusing. It explains that port forwarding is required to allow a host on the LAN to communicate with another host (a server) on the same LAN but using the public IP of that second host. That part I understand. However the article then goes on to say that modifications to the Hosts file must be made. The mods require the local LAN IP to be associated with the server. True this allows the server name to resolve to a local LAN IP but the resultant traffic remains in the LAN and never goes through the router. I don't see the need for the HOsts file. It seems to me these are two alternate solutions to the same problem. Am I missing something basic? Thanks.
Vicente

[jmizoguchi]

Originally Posted by vicente

Hi,
I read the article referenced by Jun and found it very confusing. It explains that port forwarding is required to allow a host on the LAN to communicate with another host (a server) on the same LAN but using the public IP of that second host. That part I understand. However the article then goes on to say that modifications to the Hosts file must be made. The mods require the local LAN IP to be associated with the server. True this allows the server name to resolve to a local LAN IP but the resultant traffic remains in the LAN and never goes through the router. I don't see the need for the HOsts file. It seems to me these are two alternate solutions to the same problem. Am I missing something basic? Thanks.
Vicente

this all about loopback.. accessing LAN PC from WAN side when your pc is in the same LAN network. that is loopback. if you test your server from elsewhere then you do not need to understand loopback.