locked
Remote Access - Server Site Not Available RRS feed

  • Question

  • HP MediaSmart Version: 3.3.1.35433

    Router: D-Link DGL-4500, Firmware updated.

    ISP: Comcast

    Modem: SMC Networks, SMCD3G-CCR

    External IP: 192.168.0.194

    We just moved our business from a home office location to a warehouse location and switched internet service providers. Until recently we kept our HP server up at the old location and were accessing it remotely. Recently we brought the server to the new location for convenience. But now we are unable to access the server remotely from the old location. At the new location we have Comcast as mentioned above with a D-link router hooked up to a SMC Networks modem. I used the recommended Internet Connectivity Evaluation Tool from http://www.microsoft.com/windows/using/tools/igd without any reported errors. I've called my ISP to bridge the connection to avoid the double NAT issue but the person said our connection had already been bridged. I then logged into my virtual router site to verify UPnP was enabled, and it is. Then I forwarded the TCP ports 80, 443, and 4125. When I nslookup my domain a different IP address is displayed from my IP address.

    I've attempted the following methods to access my server website.

    http://emeserver/home (Success)

    https://emeserver/remote (Success)

    http://emeserver.myhpoffice.com/home (Access Error: Site or Page Not Found)

    https://emeserver.myhpoffice.com/remote (Unable to Connect)

    http://192.168.0.194/home (Success)

    https://192.168.0.194/home (Success)

     

    I'm not sure what is going on. Any help would be greatly appreciated!

    -Clay

    Tuesday, December 27, 2011 10:51 PM

Answers

  • Results from scan of ports:
    0, 21-23, 25, 79, 80, 110,
    113, 119, 135, 139, 143,
    389, 443, 445, 1002,
    1024-1030, 1720, 5000
    0 Ports Open
    0 Ports Closed
    26 Ports Stealth
    ---------------------
    26 Ports Tested
     
    Most probably your ISP is blocking the ports your server needs to use for remote access.

    I'm not on the WHS team, I just post a lot. :)
    Wednesday, December 28, 2011 7:04 PM
    Moderator
  • https://www.emeserver.myhpoffice.com/HPHome/ gives me your HP front page from my location. Ping still gives me 108.59.160.62 but I can not see your website at that address but can at https://71.196.248.217/HPHome/ ! I can also get to your login page at both these locations - obviously I can't go any further. That to me shows that Port 80 is working which is confirmed by your ShieldsUp test. Your ISP is doing something for those two different IP addresses to be reported.

    Your Port Forwarding looks correct - have you rebooted everything (including your router). It looks as if 4125 is not working.

    If you want to create a test account with no access to any of your data, I would be happy to try to login for you.


    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.


    Wednesday, February 29, 2012 6:47 PM

All replies

  • The External IP you quote above is actually in internal IP to your network i.e. not an Internet address. The successes you are seeing above are because you are accessing via your internal network.

    Pinging emeserver.myhpoffice.com from my location returns the following IP: 108.59.160.162 - is that your external IP address (check via your router or use ShieldsUp below)?

    If you manually forward your ports as you stated above, UPnP would be better off disabled. Go to www.grc.com and run ShieldsUp to confirm that the appropriate ports are shown in "Red" as "Open". If not, your port forwarding is not working correctly.

     


    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
    Tuesday, December 27, 2011 11:05 PM
  • We just moved our business from a home office location to a warehouse location and switched internet service providers.

    How recent is "just"? If it's only a couple of hours, wait a while and try again.
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, December 28, 2011 2:02 AM
    Moderator
  • Thanks for the quick replies. 

    Ken, we moved in September actually and have been accessing the server remotely. We then moved the server from the home to the warehouse about two weeks ago and are just now getting around to fixing the remote access issue.

    Phil, my external IP address (taken from ShieldsUp) is 71.196.248.217

    I've disabled UPnP but haven't noticed a difference.

    I tested the common ports on ShieldsUp received all green boxes and the following message

      

    Results from scan of ports: 0, 21-23, 25, 79, 80, 110, 113, 
                                119, 135, 139, 143, 389, 443, 445, 
                                1002, 1024-1030, 1720, 5000
    
        0 Ports Open
        0 Ports Closed
       26 Ports Stealth
    ---------------------
       26 Ports Tested 

    I wasn't able to find port 4125 but I assume it's stealth as well.

    Thanks for the help!
    -Clay

     

    Wednesday, December 28, 2011 5:16 PM
  • Results from scan of ports:
    0, 21-23, 25, 79, 80, 110,
    113, 119, 135, 139, 143,
    389, 443, 445, 1002,
    1024-1030, 1720, 5000
    0 Ports Open
    0 Ports Closed
    26 Ports Stealth
    ---------------------
    26 Ports Tested
     
    Most probably your ISP is blocking the ports your server needs to use for remote access.

    I'm not on the WHS team, I just post a lot. :)
    Wednesday, December 28, 2011 7:04 PM
    Moderator


  • Thanks for the help! Sorry for my idiocy.

    -Clay
    Wednesday, December 28, 2011 8:54 PM
  • Also possible, and it just occurred to me: where are you testing remote access from? If you're at the same location as your server when you test, your router may not support a loopback connection.
    I'm not on the WHS team, I just post a lot. :)
    Thursday, December 29, 2011 1:26 AM
    Moderator
  • Today we added a Cisco-Linksys EZXS16W Network switch and hardwired all of our computer to the switch. We still have the D-Link wireless router connected directly to the modem. Everything works fine except for WHS remote access. Everything is the same besides the addition of the network switch. I've attempted to access the server site from all of the above domains with no success. Please help me!

    Saturday, February 25, 2012 12:58 AM
  • Clayton, if https://server/remote works (within your home network) but https://server.myhpoffice.com/remote doesn't (from anywhere), then there is nothing wrong with Windows Home Server per se. There are a number of possible issues that could cause the issue you're having; the most likely is that your ISP is blocking ports. Have you asked them about this?

    I'm not on the WHS team, I just post a lot. :)

    Sunday, February 26, 2012 2:26 AM
    Moderator
  • http://emeserver/home (Success)

    https://emeserver/remote (Success)

    http://emeserver.myhpoffice.com/home (Access Error: Site or Page Not Found)

    https://emeserver.myhpoffice.com/remote (Unable to Connect)

    http://10.1.10.16/home (Success)

    https://10.1.10.16/home (Success)

    Yes, I've check with my ISP and they confirmed that the ports are not blocked, but I was using the incorrect gateway. The IP address for the server has changed to 10.1.10.16. I went to 10.1.10.1 (default gateway) because we have hard wired all of our computers with Cat5 cables to our Comcast modem (SMC Networks, SMCD3G-CCR). I've made sure that the ports 80,443, and 4125 are forwared to 10.1.10.16.


    The WHS console tells me the remote access site is available from the web but I am still getting the above responses.

    I tried forwarding the ports according to portforward.com's instruction and created a static IP address (10.1.10.200) but that didn't seem to make any difference.


    According to GRC.com 80 and 443 are open while 4125 is stealth.

    I think I've done everything correctly, what can I be missing? Your help is greatly appreciated!

    -Clay

    Wednesday, February 29, 2012 5:57 PM
  • https://www.emeserver.myhpoffice.com/HPHome/ gives me your HP front page from my location. Ping still gives me 108.59.160.62 but I can not see your website at that address but can at https://71.196.248.217/HPHome/ ! I can also get to your login page at both these locations - obviously I can't go any further. That to me shows that Port 80 is working which is confirmed by your ShieldsUp test. Your ISP is doing something for those two different IP addresses to be reported.

    Your Port Forwarding looks correct - have you rebooted everything (including your router). It looks as if 4125 is not working.

    If you want to create a test account with no access to any of your data, I would be happy to try to login for you.


    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.


    Wednesday, February 29, 2012 6:47 PM