locked
WHS (v1.0) not updating ddns info RRS feed

  • Question

  • I have a WHS (V1.0) Server which has been working fine since early 2009, including remote access using the Microsoft "Live Domain" DDNS service. The remote access is not currently working, so I went on-site to troubleshoot. What I found was that the Windows Live Domain service was not updating with the current IP.

    The Remote Access Wizard shows the remote access "configured but not verified" and when I click on "details" I can see that the ip is incorrect, showing a valid address previously assigned by the ISP, but which as since changed. Using my laptop, if I browse to https://x.x.x.x (the correct currently assigned ISP address) the server responds properly.

    Coincidentally (although it has worked properly since) I installed a security camera setup a short while back and it has a remote access component itself, which I set up and also configured. It uses its own DDNS server which I set up, and I have the router configured to forward port 80 to the camera machine, and port 443 (and 4125) to the home server. The security system dynamic ddns is working, as is the port forwarding. I can browse externally to http://mycamera.lorexddns.net and it will take me to the security system. I can also browse to https://mycamera.lorexddns.net which, due to the port forwarding, now correctly takes me to the home server. This is fine as a workaround, but I would like to get the Windows Live Domain service working properly.

    If I ping by name, pinging mycamera.lorexddns.net pings the correct address and succeeds. If I ping myserver.homeserver.com, I can see it is pinging the older, invalid IP and of course it fails.

    So everything seems right except the ddns through the Windows Live Domain service will not update correctly, and I was unable to find a way to update it manually.

    Any suggestions as to how to get the Windows Live Domain service to update correctly?

    Thanx in advance

    PCMechanic

    Halifax, NS.

    Wednesday, December 19, 2012 3:59 PM

All replies

  • Not sure what's screwed up but WHS1 requires Port 80 to be forwarded to it (along with 443 and 4125).

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

    Wednesday, December 19, 2012 8:51 PM
  • I know port 80 is the default to respond to the http:// request, is it also required for the ddns to work? I would have thought that a utility would be running on WHS which would report the current ip to homeserver.com, and it wouldn't need a port. Am I mistaken in this?

    Thursday, December 20, 2012 2:18 PM
  • Not sure what's screwed up but WHS1 requires Port 80 to be forwarded to it (along with 443 and 4125).
    I have Port 80 forwarded to a different machine in my home, and WHS1 works fine.
     

    David Wilkinson | Visual C++ MVP
    Thursday, December 20, 2012 3:51 PM