none
Opening Homeserver.com Page (Within Local or Remote??) RRS feed

  • Question

  • Is anyone else having trouble opening their xxxx.homeserver.com page locally?  I can no longer do it from within my LAN and I was wondering of those who can no longer do it or have never been able to do it.

    What would be the point of creating a page using Whiist and then never being able to open it?   
    Friday, October 9, 2009 9:59 PM

Answers

  • if you type http://server into your web browser (if that is what you called your server at the start) you can access it locally that way
    • Marked as answer by JSHollis Wednesday, October 14, 2009 11:31 PM
    Wednesday, October 14, 2009 4:13 PM

All replies

  • Is anyone else having trouble opening their xxxx.homeserver.com page locally?

    http://xxxxx.homeserver.com has never worked for me from within my LAN (due to the way my router handles local requests).  (However, https://xxxxxx.homeserver.com does work for me from within my LAN.)

    I can no longer do it from within my LAN

    That's strange.  If it used to work, I can't think of any reason why it would no longer work for you (unless you replaced or otherwise changed something in your router).

    and I was wondering of those who can no longer do it or have never been able to do it.

    What would be the point of creating a page using Whiist and then never being able to open it?   
    The concept of Whiist (like all other tools for IIS) is that it will be used through the internet.  When you're at home, you don't need Whiist (or the internet) to view your pictures.  You can just view the pictures directly from the shares.
    Friday, October 9, 2009 10:47 PM
    Moderator
  • "That's strange.  If it used to work, I can't think of any reason why it would no longer work for you (unless you replaced or otherwise changed something in your router).



    I wish I knew.  This is really frustrating.  Could a MS update have affected this?  I did a TM Hijackthis log and saw nothing unusual.  If ports are appropriately forwarded and I had no loopback issue before are there some other settings someone is aware of to check this?


    Sunday, October 11, 2009 1:49 AM
  • I wish I knew.  This is really frustrating.  Could a MS update have affected this?

    No.

    I did a TM Hijackthis log and saw nothing unusual.  If ports are appropriately forwarded and I had no loopback issue before are there some other settings someone is aware of to check this?



    Have you tried using https://xxxxxx.homeserver.com?  Have you tried using http://server (replacing "server" with the name of your server)?
    Sunday, October 11, 2009 4:51 AM
    Moderator
  • Using http or https://xxxx.homeserver.com produces no results. http://hpserver redirects to http://hpserver/HPHome .  I tried accessing the https://xxx.homeserver.com on a different PC on my LAN and I cannot connect either.  This leads me to believe the problem lies in the 2Wire and affects outbound access to the site while allowing inbound access.

    If a recent change was made to the router to change this where would I look?
    Sunday, October 11, 2009 5:10 AM
  • Using http or https://xxxx.homeserver.com produces no results. http://hpserver redirects to http://hpserver/HPHome .  I tried accessing the https://xxx.homeserver.com on a different PC on my LAN and I cannot connect either.  This leads me to believe the problem lies in the 2Wire and affects outbound access to the site while allowing inbound access.

    If a recent change was made to the router to change this where would I look?
    Helping with setup on a specific router is outside the scope of this forum.  For that, you should check the manufacturer's website for support.
    Sunday, October 11, 2009 5:27 AM
    Moderator
  • Let me ask the question this way.  If the problem is now a loopback error (and I am not convinced it is) when it didn't used to be what caused it and can it be reversed?
    Sunday, October 11, 2009 5:30 AM
  • I have discovered this is all linked to a loopback issue after all. DSLreports.com is reporting AT&T forced a firmware upgrade and has affected this and other issues.  I have also learned I can reach my homeserver page by connecting through a proxyserver.

    Now I now the server and my PC are sound.  I may need to look into a firmware reversal or a new router that will suit my needs and they cannot update.

    Any router reccomendations?
    Monday, October 12, 2009 3:11 AM
  • As a workaround, see the following post which describes editing the "hosts" file on your PC/s to create a static entry for whatever name you want to use to point to your servers IP. http://social.microsoft.com/Forums/en-US/whssoftware/thread/03e752f3-a938-42a0-9902-068e1a67afeb

    As long as your server isn't down long enough for something else to steal its IP on your local network, it should work.
    Tuesday, October 13, 2009 6:29 PM
  • if you type http://server into your web browser (if that is what you called your server at the start) you can access it locally that way
    • Marked as answer by JSHollis Wednesday, October 14, 2009 11:31 PM
    Wednesday, October 14, 2009 4:13 PM