Like the rest of the world, or at least optimum online users, I am unable to get outside access to my LAN (webserver). Here is my setup:
I have two PCs connected to a Belkin router/hub.
The LAN ip of the first PC is 192.168.2.77. The LAN ip of the PC I am using as my server is 192.168.2.50.
The WAN IP is 68.192.114.xxx, the xxx is the same for both PCs, as it is the address assigned by optonline.
Just as I can access my router config via IE using the WAN address, I can access the router config using the LAN address. The router's godforsaken config page comes up with no issue.
I am using IIS with WinXP. I am absolutley unable to access the webserver from the outside world. Even using http://68.192.114.xxx/default.htm from the second computer, I get page cannot be displayed. I tried configuring the IIS port as 81, and when typing http://192.168.2.50:81, I CAN see the web page, but not via the WAN IP. I messed with the router's port forwarding to no avail.
ALthough I haven't tried it from outside, Ill bet if I were to try http://68.192.114.xxx from an outside computer I would be able to get to the router's config page - now, being that the config page is http based, and let's assume optonline blocks 80, why can I get to that piece of crap config page but not my webserver page?
Someone help. I'm not Cisco certified, but I am a help desk analyst, allowing me to pretend I know what I'm doing better then most.

I'm attaching a screenshot of my router's forwarding page.

RobertLn:

I split your thread out from the other, so your specific issue will get the attention it deserves. Even though related to the topic of the initial thread, piggybacking on it might keep people from looking at the thread.

-Thanks, I appreciate it.

Is there an option to set the port the router uses for the config page? If you can get to the config page on port 80 from the WAN addy and then Optonline isn't blocking port 80 traffic. Even if they are you should be ok to run the server on port 81 and the config you attached looks like it should work but I'd be concerned about a conflict with the config page or something. Also I don't like that it uses ranges...I don't trust it so I would set my range to be 81 - 81 external --forwards to--> 81 --> 81 on 192.168.1.50 or something to that effect.

I'm not sure but you might need to stick that WAN IP in on IIS too. Definitely check the IIS security and make sure you don't have it restricted to only the local net or something.

I agree, i'm not too cozy with the way you have to use ranges. I'm going to try what you suggest as it all makes sense. Thanks for the help.