By Philip Churchill on November 27th, 2007
November Update – Your Network Health Icon Will Turn Red.
After installing the new November update for Windows Home Server you will notice that your network health icon will turn red. With this update, you can now get a trusted SSL certificate for your <your_name>.HomeServer.com domain name. If you have already set up remote access via the console, settings screen, you will need to quickly unconfigure your existing sub-domain name and re-run Setup to acquire an SSL certificate for your HomeServer.com domain name.
For more details on how to accomplish this, see the following post at the official Windows Home Server Blog.
Share this WHS Article with Others:
I have jsut installed the update, since then i cant remote desktop onto my server or use the windows home server console “The computer cannot connect to the host computer” error. Even though the windows home server console icon is green and i can browse folders through windows explorer.
Hi Rob,
Try re-booting the server machine.
No issues here after the required reboot. Remote Desktop, Web Page Log in and Console all work fine. First time logging in to the Web Page via Fire Fox I had to permanently accept the certificate, but after that I can open FF or IE and get right to the landing page. Nice job MS! Thanks.
Hi TheJudge,
Same this end, no problem at all after installing the update.
Hi, this may be a lame question but here goes! I have a domain with TZO that DNS points to my IP using the TZO DDNS service.
How should I (if at all) configure the server remote access in the settings tab?
Thanks
Hi Bill,
The domain settings will only allow you to set up a xxx.homeserver.com subdomain or a few more if you have a HP MediaSmart Server. To do what you require you need to set up DDNS in your router or in the server its self. More how to do this see here.
Thanks, I already have the DDNS setup in the router. How do I make the certificate error go away when accessing the remote webpage?
Hi Bill,
The certificate is only for xxx.homeserver.com and will not work with xxx.dyndns.org or any other domain or sub-domain. So unfortunately there is no way of getting rid of the certificate errors in these cases.