locked
Remote web access not available externally RRS feed

  • Question

  • Hello,

    I'm having an odd issue after removing an old Windows Home Server box and putting a new one in its place. My old WHS box's web worked fine. I could access it at http://datasian.homeserver.com. With the new one, I set it up through the console and it passes everything except the remote connection test. Sometimes it would pass the remote connection test but I can't access it with that domain name. I tried digging further:

     - datasian.homeserver.com would resolve to my external IP address
     - Trying http://localhost/ or http://192.168.1.2 on the Windows Home Server works
     - Trying http://192.168.1.2, http://server, http://datasian.homeserver.com or http://<external ip address> fails from a computer inside the network
     - Router has ports forwarded to 192.168.1.2 in its UPNP section. I flushed it out and redid the remote access from inside the WHS console and the UPNP section got populated again.
     - Other web services seem to work fine externally: Teamspeak 3 can connect and so can uTorrent's Webui.
     - WHS's Windows firewall does have ports 55000, 80, 443 and 56000 listed. It is also set to allowed exceptions
     - Checked IIS. It is running and the website loads up fine on the WHS itself. Just nowhere else.

    Things I did after installing WHS:
     - Ran Windows Update until there were no more updates. One of the last updates it had was PP3
     - Set static IP address: 192.168.1.2, 255.255.255.0
     - Installed the add-ons PHP5 and MySQL. Tried removing them but it did not make a difference, other than it making my PHP website not work when accessed in the WHS :)
     - Installed uTorrent and set that up as a service
     - Installed Teamspeak 3 server

    Anyone know what I'm missing, maybe?

    --edit--
    Oh, error messages from web browsers:

    Chrome: 

    This webpage is not available.

    The webpage at http://datasian.homeserver.com/home/default.aspx?gotodefault=true might be temporarily down or it may have moved permanently to a new web address.

    IE:

    Internet Explorer cannot display the webpage



    Firefox:

    The connection was reset

    The connection to the server was reset while the page was loading.

        *   The site could be temporarily unavailable or too busy. Try again in a few
              moments.

        *   If you are unable to load any pages, check your computer's network
              connection.

        *   If your computer or network is protected by a firewall or proxy, make sure
              that Firefox is permitted to access the Web.


    -Dat
    Thursday, March 4, 2010 9:48 AM

All replies

  •  - Trying http://192.168.1.2, http://server, http://datasian.homeserver.com or http://<external ip address> fails from a computer inside the network
    This is your problem here - normally you would not expect to be able to use the public IP or public domain name from inside a private network but as you say you are using the IP address of your server and it's name then this points to a problem with accessing the server. 

    In your network do you have more than one router?  Do you have a firewall running on the Windows Home Server other than the built in one? 

    Does your server respond to a ping from another host?  Are you sure the network is connected, driver installed - can you access the internet from your Windows Home Server?

    You may be better off using DHCP to setup your server as you didn't say you had setup the default gateway and DNS which is what you would need to do if setting static IP.  If you dig around in your router most of them allow you to statically assign an IP via DHCP - also called Reservation, or Reserved IP.  If you give us your router make/model we can look it up.

    If it was me I would revert to DHCP and check everything works okay and then if I really wanted to use a static internal IP then makes changes once everything is confirmed working via DHCP?
    --
    Thursday, March 4, 2010 11:43 AM
  • It seems likely that something about one or more of the third party software components you've installed is causing your issue. To figure out which one, I would recommend a server reinstallation. Confirm that the server is fully functional without any of the additional software installed, then start installing things one at a time and testing extensively. Once you've identified the component causing the issue, you can hopefully figure out how to fix it. During your troubleshooting you should take notes so that should you ever need to recover your server again (due to e.g. OS corruption) you'll know the particulars of this issue.

    Al may be right about the internal vs. external access, by the way. A lot of consumer routers have trouble with loopback connections, where a device inside the local network tries to access the external IP address of the router.

    I'm not on the WHS team, I just post a lot. :)
    Thursday, March 4, 2010 3:30 PM
    Moderator
  • I did set up a default gateway and DNS. Both are my router (192.168.1.1). It seems that I can ping it.

    C:\Users\DatAsian>ping 192.168.1.2

    Pinging 192.168.1.2 with 32 bytes of data:
    Reply from 192.168.1.2: bytes=32 time=1ms TTL=128
    Reply from 192.168.1.2: bytes=32 time=1ms TTL=128
    Reply from 192.168.1.2: bytes=32 time=1ms TTL=128
    Reply from 192.168.1.2: bytes=32 time=1ms TTL=128

    Ping statistics for 192.168.1.2:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 1ms, Maximum = 1ms, Average = 1ms

    I can access the internet from the WHS. No antivirus or firewall programs were installed on the home server, and Windows Firewall was never modified. 

    I can try Ken's option and just do a server reinstall. I just need to back up stuff first :)

    -Dat
    Friday, March 5, 2010 3:57 PM
  • Ensure you don't have any proxy settings on the client computers when you are trying to connect to the server.  Also a server recovery (not reinstall) will preserve the data in your shares.


    --
    Friday, March 5, 2010 4:55 PM
  • Can you open the website from the server desktop?
    Does the site http://yourshortservername:55000 come up properly?
    Did any of the applications you installed alter settings in IIS (Internet Information Server) in the direction, that it is no longer at WHS defaults? This can be an own website, altered permissions (check the server event log for that) or a wrong version of .NET Framework set.
    Best greetings from Germany
    Olaf
    Friday, March 5, 2010 9:21 PM
    Moderator
  • http://server:55000 wasn't responsive, but http://server:8080/gui (utorrent webui) works fine. Just got done reinstalling WHS. I think I found where it is not working by accident:

    It seems that a combination of turning on my Windows Home Server's ethernet card's Jumbo Frames (RTL8168) feature to 9k will slow IIS down to a crawl. Going to http://datasian.homeserver.com, http://server and http://192.168.1.2 would intermittently fail. If it wouldn't fail, it would load very slowly (about 3 minutes to refresh the front page). Going to IIS and setting a bandwidth throttle completely kill it. Disabling Jumbo Frames will make everything super snappy again.

    The whole time, going to the Windows Home Server and going to http://localhost performs with no issues.   

    I have a gigabit network at home and the switches support 9k. I can turn it off but I'll miss the very decent performance bump. I miss my other home server now :P

    -Dat
    Saturday, March 6, 2010 1:02 AM
  • ...
    It seems that a combination of turning on my Windows Home Server's ethernet card's Jumbo Frames (RTL8168) feature to 9k will slow IIS down to a crawl.
    ...
    This article may help you understand the perils of jumbo frames. Not that jumbo frames are inherently bad, but it's very possible to cause serious network issues with them...
    I'm not on the WHS team, I just post a lot. :)
    Saturday, March 6, 2010 4:24 AM
    Moderator
  • Thanks for the article :)

    Now I'm curious if this NIC is playing a role on it? That'll be experimenting for another day; everything is working right now so I won't mess with it. Thanks again.

    -Dat
    Saturday, March 6, 2010 4:57 PM