Jonas Svenson has just posted over at the Windows Home Server Blog that our WHS that use homeserver.com as domain names may have issues tomorrow as their service migrates to the Azure platform. If your IP is static then you should still have Remote Access tomorrow however, if it changes, you will not be able to access your server remotely until Wednesday. Read on and follow the link to find out more.
My friend and fellow Windows Home Server MVP Sam Wood has just announced a closed beta for his new Add-In called Feedsource for Windows Home Server V1, and as usual it’s cool!
HP have released an add-in for Windows Home Server that makes it easy to transfer files to and from external USB drives – but it is only for HP Windows Home Servers. Here is our review.
Want to know what to expect when setting up Remote Access for the Vail beta? John “Diehard” Zajdler and I set up Remote Access on my Windows Home Server Vail beta and made a short video of the process.
A few days ago, Richard, one of our readers asked a question about using his own domain name with Windows Home Server instead of either the TZO.com or the Homeserver.com address.
Another step along the way to having remote access for your Windows Home Server is that you need to select a personalized domain name for your Windows Home Server which makes it easier for you to remember the URL to connect to your Windows Home Server when you are away from home.
If your broadband router doesn’t support UPnP or cannot be configured automatically, don’t worry, you can manually configure the port forwarding on your router, it’s just quicker and easy if it’s all done for you.
