No announcement yet.

Home Web server problems

  • Filter
  • Time
  • Show
Clear All
new posts

  • Home Web server problems

    I'm having a go at setting up one of my old PC's as as web server, and I'm having a little problem getting through my router. I've got apache up and running fine, and I've assigned a domain name to my server. I'm forwarding port 80 (the internet) to my local server box's IP, and dynamic DNS is set up as well. I can connect fine inside my local network, but when I try to use my actual WAN IP address or through my domain name I can't get a connection. The IP on the LAN works fine, but I need to connect to my WAN IP, not the LAN.

    If I completely bypass my router everything works fine, it's just going through the router that I have problems. Anyone have any idea what I'm doing wrong? And if you need more info let me know, I'm still a bit new at networking. :)

    I didn't join a squad once and this guy named Nardini took me into the back room and beat me with a sock of oranges.

  • #2
    Re: Home Web server problems

    Hard to know on the outside looking in with all the possibilities. What kind of router and firewall? Since you have a static IP for the server you may have to change some of the "allow incoming vs outgoing" ping, etc., in the advanced options in your router. You may also have to change firewall settings also to make the server a "safe" or "trusted" zone. My first guess since you can connect within your network but not outside/in is that you have router settings
    blocking outside ping or echo and the server cannot be seen. You may be able to allow those settings just within that zone so you do not open up the rest of your network. Total guesses without knowing your setup.


    • #3
      Re: Home Web server problems

      I'm not sure of the brand name of the router, bought it a few years ago and all it says is "WLAN" on both the router itself and the router setup page. I'm just using Windows firewall right now but I've had that disabled until I can figure out what's going on with the router first. As far as settings, I've got all of these checked:
      Enable uPNP
      Enable Ping Access on WAN
      Enable Web Server Access on WAN
      Enable IPsec pass through on VPN connection
      Enable PPTP pass through on VPN connection
      Enable L2TP pass through on VPN connection

      Regarding the router's firewall I've got these options:
      Port Filtering
      IP Filtering
      MAC Filtering
      Port Forwarding
      URL Filtering

      Port forwarding and DMZ are already configured, and the others don't apply.

      I've also tried making the server box the DMZ, so that should open all ports to that box, correct?

      One more thing, I was messing around with the port forwarding, and if I open up port 80 to the router's IP address (, I was able to log on to the router setup screen when I type in my domain on any computer. If I open port 80 on my server box's IP ( nothing works. I can't open up port 80 on both IP's or I get an error saying "Setting port range has overlapped with used port numbers!" Also, my router seems to be set up for fixed IP, not static IP.
      Last edited by thegreatnardini; 01-20-2008, 02:16 AM.

      I didn't join a squad once and this guy named Nardini took me into the back room and beat me with a sock of oranges.


      • #4
        Re: Home Web server problems

        Your ISP probably filters out all incoming ports 1023 and below to keep you from running a server. As a test, add a router rule to forward port 4321 to the web server internal ip port 80. Then run your test adding the new port number to the url like so and see if that passes. If it does then its the ISP blocking the standard service ports.

        I used to be with Armstrong cable here in Ohio. They did this. I am now with Time Warner Cable, and they don't filter anything.


        • #5
          Re: Home Web server problems

          I installed a new router today and came across this.
          It may help.

          Virtual Server

          The Virtual Server option gives Internet users access to services on your LAN. This feature is useful for hosting online services such as FTP, Web, or game servers. For each Virtual Server, you define a public port on your router for redirection to an internal LAN IP Address and LAN port.

          You are hosting a Web Server on a PC that has LAN IP Address of and your ISP is blocking Port 80.

          1. Name the Virtual Server (for example: Web Server)
          2. Enter the IP Address of the machine on your LAN (for example:
          3. Enter the Private Port as [80]
          4. Enter the Public Port as [8888]
          5. Select the Protocol (for example TCP).
          6. Ensure the schedule is set to Always
          7. Click Save to add the settings to the Virtual Servers List
          8. Repeat these steps for each Virtual Server Rule you wish to add. After the list is complete, click Save Settings at the top of the page.

          With this Virtual Server entry, all Internet traffic on Port 8888 will be redirected to your internal web server on port 80 at IP Address

          Virtual Server Parameters

          Assign a meaningful name to the virtual server, for example Web Server. Several well-known types of virtual server are available from the "Application Name" drop-down list. Selecting one of these entries fills some of the remaining parameters with standard values for that type of server.
          IP Address
          The IP address of the system on your internal network that will provide the virtual service, for example You can select a computer from the list of DHCP clients in the "Computer Name" drop-down menu, or you can manually enter the IP address of the server computer.
          Traffic Type
          Select the protocol used by the service. The common choices -- UDP, TCP, and both UDP and TCP -- can be selected from the drop-down menu. To specify any other protocol, select "Other" from the list, then enter the corresponding protocol number ( as assigned by the IANA) in the Protocol box.
          Private Port
          The port that will be used on your internal network.
          Public Port
          The port that will be accessed from the Internet.
          Inbound Filter
          Select a filter that controls access as needed for this virtual server. If you do not see the filter you need in the list of filters, go to the Advanced → Inbound Filter screen and create a new filter.
          Select a schedule for when the service will be enabled. If you do not see the schedule you need in the list of schedules, go to the Tools → Schedules screen and create a new schedule.

          24 -- Virtual Servers List
          Use the checkboxes at the left to activate or deactivate completed Virtual Server entries.

          Note: You might have trouble accessing a virtual server using its public identity (WAN-side IP-address of the gateway or its dynamic DNS name) from a machine on the LAN. Your requests may not be looped back or you may be redirected to the "Forbidden" page.

          This will happen if you have an Access Control Rule configured for this LAN machine.

          The requests from the LAN machine will not be looped back if Internet access is blocked at the time of access. To work around this problem, access the LAN machine using its LAN-side identity.

          Requests may be redirected to the "Forbidden" page if web access for the LAN machine is restricted by an Access Control Rule. Add the WAN-side identity (WAN-side IP-address of the router or its dynamic DNS name) on the Advanced → Web Filter screen to work around this problem.




          TeamSpeak 3 Server




          Twitter Feed