Member Avatar for RobertLn

i had the same problem, ensuing in a big headache one day I couldnt figure out why i couldnt get anyone outside my LAN to access IIS 5

then i used port 81 and it worked....

i wouldnt be surprised if optonline blocked the web port

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 from the second computer, I get page cannot be displayed. I tried configuring the IIS port as 81, and when typing , 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 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.

  • 3 Contributors
  • 4 Replies
  • 200 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by RobertLn

Dani AI

Generated

Quick, practical checklist for the situation described by (IIS serves locally, IIS moved to port 81 works on the LAN, router config is reachable from the WAN but the site is not). The three usual culprits are: (A) the router’s remote-management/web-admin is intercepting port 80 from the WAN, (B) the ISP blocks incoming port 80 on residential accounts, or (C) the router does not hairpin (NAT loopback), so testing the WAN IP from inside the LAN gives misleading results.

Server-side verification (run these on the XP machine acting as the server):

ipconfig /all
netstat -an | find ":80"
netstat -an | find ":81"    (if using port 81)

Confirm the site responds to http://localhost/ and to the server’s LAN IP from another LAN PC. In IIS Manager check the site’s binding — set IP to “All Unassigned” (or the server’s LAN IP) and confirm the port and any host headers are correct. Give the server a static LAN IP or a DHCP reservation so forwarding always points to the right host. Also check Windows XP firewall or any third-party firewall to allow inbound TCP on the chosen port.

Router-side and forwarding tips: disable remote/remote-management (or move it off port 80) so the router won’t answer WAN:80 itself. In the router’s Virtual Server / Port Forwarding set a single-port rule (avoid ranges) such as External 80 → Internal 80 (TCP) → 192.168.2.50, or if the ISP blocks 80 use External 81 → Internal 80 and connect externally to http://<WANIP>:81. If the GUI forces a range, use 81–81 (external) → 81–81 (internal) → 192.168.2.50 as suggested. As a quick test, enable DMZ for the server only to see if the site becomes reachable (turn DMZ off after testing).

Final checks and cautions: test from a truly external host (friend’s PC or mobile data) — many routers won’t forward when testing from inside. If everything above fails, contact the ISP about blocked ports or get a business/static option. Leaving router remote management open to the WAN is a security risk; close it and ensure IIS is patched and hardened before exposing it to the Internet.

Recommended Answers

All 4 Replies

Member Avatar for alc6379

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.

Member Avatar for RobertLn

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.

Member Avatar for antioed

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 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.

Member Avatar for RobertLn

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.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.