I have verizon DSL, and basically forwarding all traffic to my MR314. I have a webserver running IIS behind it (not really important at this point). I have port 80 forwarded to the LAN IP of the webserver. When I hit the WAN IP in the address bar, the router GUI is accessed, and the traffic isn't forwarded. What am I missing? I've hosted this server before with no troubles, so I know what I'm doing. I just don't know what I'm missing. The IP Address is dynamic, and I'm running ver 3.29 Firmware on the router.

Classic problem, and occurs on a router-by-router basis. The problem is that your SOHO router configuration interface is running on TCP 80, as well as your web server. On certain brands and models of SOHO routers, that TCP 80 connection will allocate priority to your router configuration interface when the traffic is viewed as "incoming", from the LAN side of the network. My guess is that if you were to have a friend type in your WAN IP from somewhere on the Internet, they would see your IIS Server home page. If you have the ability to change the web server port of your router configuration interface, I would try doing that first. If you do not have that ability, the only way to access your IIS server from the LAN-side is to type in its local address in your browser.

I agree with Smitty, its all down the particular router you have. I had the same problem with D-Link router. The only way I could access my own web server was via a local IP address. A URL or Public address gave me the router interface. The D-link documentation told me that what I was trying to do was impossible. However, with a Belkin router no such problem. I can access my web server with a public IP address or URL from within my own network, but I can't access it via a local IP address. Stuart

I have since bridged my verizon-supplied router, and all dhcp, nat, authentication etc is done through my MR314...I'll see if the website can be hit from the outside world. I'm also using no-ip.com, so if anyone wants to hit proofread.redirectme.net from the outside and post the results, let me know what you find. Thanks for the insight

Tried proofread.redirectme.net. Not found. Stuart

Alright, thanks..I'll have one of my buddies test it out with me then. At least I got it to show on the local side, and its no longer pulling up the router GUI. Thanks for help!

The ISP blocks port 80. I changed the port in IIS and the port forwarding, and everything works beautifully.