locked
Can access homeserver.com Landing Page but NOT the Home Page RRS feed

  • Question

  • I've just reinstalled WHS v1 on my server, following a HDD crash after nearly five years.  Now, I can get to my homeserver.com landing page, but the home ('log on') page is 'not available':
     
    http://<domain>.homeserver.com/home/ - works
    https://<domain>.homeserver.com/remote/ - page not available
     
    I also tried using my IP Address:
     
    http://<ip-address>/home/ - works
    https://<ip-address>/remote/ - page not available
     
    If I try locally, using the server name, I can get to both the landing page and the home page (and I can log in successfully):
     
    http://<servername>/home/ - works
    https://<servername>/remote/ - works
     
    Port forwarding has been set up on my router (BT Home Hub 3) for http, https and rdp (port 4125).  This was working fine before the rebuild, and has not been changed since.  (I have restarted the home hub to be sure).
     
    I am using a different homeserver domain name (because I couldn't reconfigure WHS to use the old one), but don't see why this should be significant.
     
    Does anybody have any suggestions as to what might be the problem?
     
    Thanks for your help.

    • Edited by IceColdUK Wednesday, July 3, 2013 11:41 PM
    Wednesday, July 3, 2013 11:38 PM

All replies

  • This is a complete new installation? Does your new server have the same internal IP address as the old? Try ShieldsUp at www.grc.com to ensure the ports are actually forwarded correctly.

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


    Thursday, July 4, 2013 12:56 AM
  • Thanks for the reply, Phil.

    Yes, a completely fresh install to a new HDD, but I don't think the internal IP Address changed.  Either way, I've gone through the port forwarding set up on my router from scratch - creating a new application, "WHS RDP" for port 4125, and assigning this, HTTP and HTTPS to the server's IP Address.  But no difference. :-(

    According to ShieldsUP! ports 80 and 443 are both open, but if I probe port 4125, this is shown as closed (Unknown Protocol for this port / Unknown Application for this port).  Should this be shown as open too?

    Thanks,
    Richard
    Thursday, July 4, 2013 3:39 PM
  • Yes, for WHS1 you need Port 4125. Sounds as though "WHS RDP" is not working.

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


    • Edited by Phil Harrison Thursday, July 4, 2013 10:53 PM Additional comment
    Thursday, July 4, 2013 7:49 PM