locked
Cannot Connect To mydomain.homeserver.com RRS feed

Answers

  • I modified the hosts file.  All is well in the world again.
    • Marked as answer by JSHollis Wednesday, October 14, 2009 11:30 PM
    Wednesday, October 14, 2009 11:30 PM

All replies

  • Remote Access is available as shown in the console. I still cannot connect to my homeserver site. I've rebooted the server and my router.  This morning my 2Wire was telling me it detected "router behind a router".  It prompted me to disable or resolve. Resolve wanted to place my main PC in DMZ. I was able to resolve most things but not connecting to the homeserver site.  I can access the server on my LAN using http://hpserver/HPHome/ . 

    I am also getting the dialog box below when trying to repair a connection here http://img40.imageshack.us/img40/4069/dialog2.jpg

    http://img14.imageshack.us/img14/7937/dialogk.jpg

    When I open the page it goes to http://www.microsoft.com/en/us/default.aspx

    Are those pics from your server desktop (or a client)?

    Are you trying it from outside your LAN?  If not, please do that (and try from somewhere other than work as some businesses block ports needed by WHS, such as a Starbucks or a friend's house).  If it still doesn't work, go to Shields Up! and do a custom port scan for 80, 443, and 4125, then post the results here.
    Monday, September 28, 2009 5:35 PM
    Moderator
  • Images are on the client machine.
    Monday, September 28, 2009 6:47 PM
  • Here are additional images from the client machine.  My 2Wire does report that ports 80, 4125, and 443 are configured.  My wife was able to access the server today. I used to a week or so ago from the homeserver.com site.

    I am not sure what is meant by a remote firewall.

    http://img62.imageshack.us/img62/765/network.jpg


    Here is how the router is configured http://img525.imageshack.us/img525/8189/ports.jpg


    Just today my wife said she was able to access a page we created on the server xxxxxx.homeserver.com/xxxxxxx
    Tuesday, September 29, 2009 5:16 AM
  • Here are additional images from the client machine.  My 2Wire does report that ports 80, 4125, and 443 are configured.  My wife was able to access the server today. I used to a week or so ago from the homeserver.com site.

    I am not sure what is meant by a remote firewall.

    http://img62.imageshack.us/img62/765/network.jpg


    Here is how the router is configured http://img525.imageshack.us/img525/8189/ports.jpg


    Just today my wife said she was able to access a page we created on the server xxxxxx.homeserver.com/xxxxxxx
    Well, if it's working for your wife, it's not a problem with your server (but wherever you are trying to connect from).
    Wednesday, September 30, 2009 4:40 AM
    Moderator
  • Just today my wife said she was able to access a page we created on the server xxxxxx.homeserver.com/xxxxxxx

    If you created custom pages it's very well possible you made some error, messing up whs remote access. If that happened server reinstall is probably your best option to fix this issue.
    Wednesday, September 30, 2009 11:12 PM
    Moderator
  • The page was created before the problem.  It has nothing to do with my issue.  This I am sure of. 
    Sunday, October 4, 2009 12:37 AM
  • I am still not able to connect the way I did before just a week ago.  Who can I show my router config to?  I'd rather not post the config here.

    I am obviously missing something somewhere.
    Sunday, October 4, 2009 12:58 AM
  • The page was created before the problem.  It has nothing to do with my issue.  This I am sure of. 

    If the page was created before the problem started (and the problem started immediately afterwards), it could very well be the root cause.
    Sunday, October 4, 2009 1:31 AM
    Moderator
  • I am still not able to connect the way I did before just a week ago.  Who can I show my router config to?  I'd rather not post the config here.

    If you don't want to post it here, I don't see how anyone here can really help.  :)  Besides, there is nothing of any significance in it anyway (with the possible exception of your external IP address, which you can just xxx out if you want).

    I am obviously missing something somewhere.

    Going back to what you said before, you said, "My wife was able to access the server today."  Is it still working for her?  If so, what exactly is the problem?  Please be specific.
    Sunday, October 4, 2009 1:36 AM
    Moderator
  • yes but long before the problem.  Both the page and access to the homeserver.com worked fine until recently.  No pages have been created recently.
    Sunday, October 4, 2009 1:37 AM
  • Take a look at the 2wire config http://img27.imageshack.us/img27/8777/2wire.jpg
    Sunday, October 4, 2009 1:45 AM
  • Take a look at the 2wire config http://img27.imageshack.us/img27/8777/2wire.jpg

    That doesn't really help at all.  It doesn't show the IP address of your server (only your external IP address).  However, you still didn't answer the question:  Is it working for your wife now?  You said it was before.  Also, please go to the Shields Up! link I posted before and do the port scan I requested.
    Sunday, October 4, 2009 1:59 AM
    Moderator
  • She did last week from work.  Don't know if that's still the case as its the weekend. I would only PM my homeserver.com address.  I know my servers address doesn't show in the image and I know that's part of the problem. By why? ports appear forwarded but all to the external but not the internal.  Does this help?

    Shields Up reported.


    80

    OPEN!
    http
    World Wide Web HTTP


    443

    OPEN!
    https
    http protocol over TLS/SSL


    4125

    Closed
    Unknown Protocol for this port
    Unknown Application for this port

    Sunday, October 4, 2009 2:25 AM
  • She did last week from work.  Don't know if that's still the case as its the weekend. I would only PM my homeserver.com address.  I know my servers address doesn't show in the image and I know that's part of the problem. By why? ports appear forwarded but all to the external but not the internal.  Does this help?

    Shields Up reported.

     


    80

    OPEN!
    http
    World Wide Web HTTP

     

     


    443

    OPEN!
    https
    http protocol over TLS/SSL

     

     


    4125

    Closed
    Unknown Protocol for this port
    Unknown Application for this port

     

    Good, those are the results you should have from Shields Up!  Based on that, I would suggest you try your Remote Access website again.  Make sure you do it from A) outside your LAN and B) somewhere that won't block outgoing ports (such as a friend's house or a Starbucks).
    Sunday, October 4, 2009 3:29 AM
    Moderator
  • My father was able to open my homeserver.com page and everything looks good here to.
    http://img251.imageshack.us/img251/6313/domainnameconfig.jpg

    So.. why can't I open the homeserver page?  I 've been able to before.
    Monday, October 5, 2009 12:36 AM
  • My father was able to open my homeserver.com page and everything looks good here to.
    http://img251.imageshack.us/img251/6313/domainnameconfig.jpg

    So.. why can't I open the homeserver page?  I 've been able to before.
    Where are you trying to open it from?
    Monday, October 5, 2009 3:01 AM
    Moderator
  • My home (and within my LAN) and I've had no issues doing so.  In fact locally I cannot access things like websharefolders via my browser.


     
    Monday, October 5, 2009 3:14 AM
  • From within your home, which name did you try?
    http://servername
    or
    http://internetservername.homeserver.com?
    The short name should work from within your home, while the long name depends from the Loopback capabilities of your router. Not each router supports accessing the internal network from the same internal network via Internet.
    Best greetings from Germany
    Olaf
    Monday, October 5, 2009 7:02 AM
    Moderator
  • Yes I can open my server locally but not my october.homeserver.com site or anything off it like homeserver.com/october or homeserver.com/november.

    My router doesnt appear to have any loopback issues as I have been able to access the following BEFORE but am not able to NOW.

    https://october.homeserver.com

    http://october.homeserver.com/october

     
    Monday, October 5, 2009 12:26 PM
  • Hi,
    he only access supported via IIS is the usage of the remote access website, which should shown by calling the website only, but not deep links directed to folders, as your second link would make me assume.
    (Assuming, that october is the name, which you registered as domain name with your live ID, and not the internal short name.)
    Best greetings from Germany
    Olaf
    Monday, October 5, 2009 12:34 PM
    Moderator
  • When I try to open my xxxx.homeserver.com page I get this  but my 2Wire page shows this port open and forwarded.

    • Edited by JSHollis Thursday, October 8, 2009 2:22 AM
    Monday, October 5, 2009 2:53 PM
  • When I try to open my xxxx.homeserver.com page I get this http://img25.imageshack.us/img25/4825/443a.jpg but my 2Wire page shows this port open and forwarded.


    You may need to specifically allow this port in the router firewall.
    Monday, October 5, 2009 2:59 PM
    Moderator
  • Monday, October 5, 2009 3:05 PM
  • Your server is reachable from here.
    (Used the name in one of the pictures.)
    Edit: Just tried again from home, which also presents the HP Media Smart Server Home page (HTTP), and clicking on one of those pages, which require login, also opens smoothly via HTTPS.

    So I assume, your problem is not a real problem, but obviously location based.

    Best greetings from Germany
    Olaf
    Monday, October 5, 2009 3:12 PM
    Moderator
  • Your server is reachable from here.
    (Used the name in one of the pictures.)
    Best greetings from Germany
    Olaf
    Last week I was unable to get to [myserver].homeserver.com.

    Turned out I had fat-fingered the IP address assigned to the server.

    I had set up HomeServer, when it's IP was 192.168.0.102 and, when fooling around with one of the routers, managed to set it to 192.168.0.108.

    Fixed the address, and was able to connect.
    Monday, October 5, 2009 5:13 PM
  • That's not the case here.
    Monday, October 5, 2009 10:30 PM
  • Anyone else have something to add.  It appears folks can access my homeserver.com page but I cannot.  Nor can I open any pages I've created in the past.  In my opinion then it's not the pages and not the homeserver.com page but rather something onboard my PC, the server, or a 2Wire router config. 

    It would seem though the router config would have to be correctly configured or else it would effect in/out traffic.

    I am stumped and cannot figure out what the block is. It is not a loopback issue.  

    Are there any diagnostic tools to run to ferret out the culprit?


     Addendum:  I did a traceroute and it's saying destination reached but router did not respond.

    Tuesday, October 6, 2009 1:47 AM
  • That's been done.  See here http://img27.imageshack.us/img27/8777/2wire.jpg


    Sure? I'm not familiar with your modem, however based on the image you only allow access from one IP address (xxx.xx.190.167) or this IP represents your external IP address. IF it's the latter please re-configure, since your server is reachable on xxx.xx.183.205. (Like Olaf I can reach your server using  http:\\xxxxxxxx.homeserver.com 

    Perhaps your external IP address changed causing the firewall to be configured incorrectly.

    EDIT: Could also be IP address changed and your local DNS cache is not updated. Please try open command prompt and run the following command: ipconfig /flushdns. Also please try rebooting your router.

    NOTE. Once you solved your problem it may be advisable to remove all references to your whs domain name and IP address from this thread. If you want I can do this for those posts you can not access.
    Tuesday, October 6, 2009 2:22 AM
    Moderator
  • "IF it's the latter please re-configure, since your server is reachable on xxx.xx.183.205. (Like Olaf I can reach your server using  http:\\xxxxxxxx.homeserver.com"

    I did the flush.

    I reconfiged and this resulted.  
    http://img3.imageshack.us/img3/2770/scrff.jpg

    Even after refresh nothing changed.  I also rebooted router.  Back to square one. 
    Tuesday, October 6, 2009 10:35 PM
  • Can anyone tell me why this dialog box tells me to port forward 443 when it is already forwarded?

    http://img200.imageshack.us/img200/2216/443qs.jpg

    I reset the router and reconfigured but I still CANNOT  reach my homeserver.com page which obviously affects my ability to reach any pages I've created.


    Please don't give up on this forum as I need to resolve this.

    Anyone familiar with 2Wire routers?
    Thursday, October 8, 2009 2:36 AM
  • Maybe your ISP changed something, so that loopback does not work longer (in case your router did indeed support this)? Or did you upgrade the router (changed hardware or applied firmware upgrade - the later may happen also automatically if configured that way)?
    More than speculation is not possible from here. Especially since we can see the product working, and I am sure with proper credentials also a login would be fully functional.
    What is the reason for not wanting to use the local (short-)name from home?
    Best greetings from Germany
    Olaf
    Thursday, October 8, 2009 2:11 PM
    Moderator
  • I cannot connect to homeserver.com page. 2Wire shows all ports (80, 443, 4125) forwarded.  Two different port tools (Shields Up, DynDNS) show port 443 blocked/refused. AT&T said they are not blocking.  2Wire said the issue may lie in the client PC.  

    Any ideas? Any further tools to diagnose the client PC with.  Would reinstalling the server software of the client PC help at all?  This is chapping my ____ not being able to resolve this.  

    Thanks for the help
    Thursday, October 8, 2009 9:40 PM
  • Would reinstalling the server software of the client PC help at all?  This is chapping my ____ not being able to resolve this.  

    Since other people can connect to your home server and your ISP says, he doesnt block anything, the router no loopback support or eventually some locally installed security software is remaining.
    Installing the connector software has nothing to do with Remote Access (you don't install it on a PC which tries to connect via Internet either.
    Best greetings from Germany
    Olaf
    Friday, October 9, 2009 7:18 AM
    Moderator
  • 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:10 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. 

    Any router reccomendations?

    so one of my earlier assumptions about a firmware upgrade as possible reason was correct.

    At home I use the Fritz!Box 7270 - but recommendations should be done more on a regional base, since warranty and all this stuff may also play a role.

    Best greetings from Germany
    Olaf
    Monday, October 12, 2009 12:34 PM
    Moderator
  • I modified the hosts file.  All is well in the world again.
    • Marked as answer by JSHollis Wednesday, October 14, 2009 11:30 PM
    Wednesday, October 14, 2009 11:30 PM