none
Internet Access problem with WHS RRS feed

  • Question

  • I have been attempting to setup my remote website on windows home server, local access is fine, remote web access is unavailable, and unrepairable with the WHS repair tool.
    I have forwrded ports 80,443 and 4125 TCP protocol to my servers IP. No Luck, I've checked with my ISP, Road Runner through Brighthouse Networks, they claim that servers are allowed and they do no block any ports. I've used Shields up web site and after scanning the first 1056 ports all ports show up as STEALTH mode except one, port 22 thats shows up as closed.
    What am I missing, why can't I get this setup correctly, I'm not a Novice PC user, I've been building, upgrading and reparing Windows PC's for over 10 years.
    Tuesday, May 26, 2009 8:46 PM

Answers

  • If all ports are showing STEALTH (you don't mention testing 4125, what about that one?), then something is blocking the traffic on those ports. There are several possibilities. In no particular order:
    • Perhaps you didn't correctly forward the ports? This is easier than you think to do. :)
    • Do you have a broadband modem that acts as a router? This would cause a "double NAT" situation with normal default configurations, and will usually lead to all ports seeming to be blocked. You can usually determine if this is a factor by looking at your reported IP address on a site such as Shields Up!, and in your router's configuration app (where it's often referred to as something like "WAN IP address") to make sure they're the same. The way to correct this is to put your broadband modem into "bridge" or "passthrough" mode.
    • Your ISP may, for reasons of economy, be using private addressing on their own network. This would also lead to a "double NAT" situation.
    • Your ISP may be blocking ports, no matter what they tell you.

    I'm not on the WHS team, I just post a lot. :)
    Tuesday, May 26, 2009 9:04 PM
    Moderator
  • There is one final thing you should look at: if you have not done so yet, you should test your remote access from some locaiton other than your home. Many consumer routers can't deal with a request from inside their network that "loops back" through the external network interface. If you haven't, take a laptop to a Starbucks or your local public library and give it a try.
    I'm not on the WHS team, I just post a lot. :)
    Tuesday, May 26, 2009 9:29 PM
    Moderator

All replies

  • If all ports are showing STEALTH (you don't mention testing 4125, what about that one?), then something is blocking the traffic on those ports. There are several possibilities. In no particular order:
    • Perhaps you didn't correctly forward the ports? This is easier than you think to do. :)
    • Do you have a broadband modem that acts as a router? This would cause a "double NAT" situation with normal default configurations, and will usually lead to all ports seeming to be blocked. You can usually determine if this is a factor by looking at your reported IP address on a site such as Shields Up!, and in your router's configuration app (where it's often referred to as something like "WAN IP address") to make sure they're the same. The way to correct this is to put your broadband modem into "bridge" or "passthrough" mode.
    • Your ISP may, for reasons of economy, be using private addressing on their own network. This would also lead to a "double NAT" situation.
    • Your ISP may be blocking ports, no matter what they tell you.

    I'm not on the WHS team, I just post a lot. :)
    Tuesday, May 26, 2009 9:04 PM
    Moderator
  • I have been attempting to setup my remote website on windows home server, local access is fine, remote web access is unavailable, and unrepairable with the WHS repair tool.
    I have forwrded ports 80,443 and 4125 TCP protocol to my servers IP. No Luck, I've checked with my ISP, Road Runner through Brighthouse Networks, they claim that servers are allowed and they do no block any ports. I've used Shields up web site and after scanning the first 1056 ports all ports show up as STEALTH mode except one, port 22 thats shows up as closed.
    What am I missing, why can't I get this setup correctly, I'm not a Novice PC user, I've been building, upgrading and reparing Windows PC's for over 10 years.

    Ken has provided you with pretty much all the reasons why this might not be working.  Doing a quick search, it looks like you may be blocked on port 80 but I can't say for sure.  There are alternatives but be warned that you may be violating your TOS with the ISP if it is in the written contract.
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Tuesday, May 26, 2009 9:16 PM
    Moderator
  • There is one final thing you should look at: if you have not done so yet, you should test your remote access from some locaiton other than your home. Many consumer routers can't deal with a request from inside their network that "loops back" through the external network interface. If you haven't, take a laptop to a Starbucks or your local public library and give it a try.
    I'm not on the WHS team, I just post a lot. :)
    Tuesday, May 26, 2009 9:29 PM
    Moderator