Comments on: Windows Home Server Nirvana Is One Step Closer

By: Christoph

Christoph — Fri, 13 Aug 2010 06:18:10 +0000

You don't need to use dyndns or similar. You simply need to open the 8080 and 4443 port in the firewall of you WHS.

By: Hammer

Hammer — Sun, 03 Jan 2010 07:37:55 +0000

In my case it’s because I already have a valid domain name that I’ve been using for a number of years. I don’t want to use something else since everyone knows it already.

By: James

James — Wed, 07 Oct 2009 20:45:53 +0000

Fortunately (heh) I already have FiOS. This is still an issue for me. Did the problem go away for you after switching to FiOS? If so, how?

By: Kevin C. Tofel

Kevin C. Tofel — Wed, 07 Oct 2009 19:15:41 +0000

Unfortuantely (or fortunately, depending your POV), I switched over from DSL to FiOS before resolving the issue. I no longer have this issue, as a result. One of the dynamic DNS services mentioned above might help.

By: James

James — Wed, 07 Oct 2009 18:30:30 +0000

“I can’t yet access my WHS box through my custom homeserver.com domain. Instead, I have to navigate to it by using the WAN IP address provided by Verizon Wireless. For example, if Verizon assigns the IP of 185.123.4.5 to my DSL connection, I have to type https://185.123.4.5:4443 to get to my WHS box. Obviously that’s not ideal because it’s clunky and more importantly, it becomes useless the minute Verizon changes the IP address I’ve been assigned.”

Did you ever solve this issue? It matches my problem exactly and I’m a bit stumped.

By: oVan

oVan — Wed, 03 Jun 2009 07:14:42 +0000

If your ISP blocks port 80 and/or 443, you don’t need to change the port numbers in IIS:

Instead of configuring your router to forward port 8080 and 4443 to the same ports on your WHS, let it forward them to port 80 & 443. Most routers allow you to define virtual servers where you can define incoming and outgoing port differently. No changes on the WHS/IIS side needed.

By: Kevin C. Tofel

Kevin C. Tofel — Sat, 30 May 2009 13:45:53 +0000

This is precisely why I’d rather not go with a third-party DDNS service if I can help it. I’d rather use the native function. :)

By: Ben

Ben — Sat, 30 May 2009 13:28:55 +0000

It shocks me how many commenters don’t realize that WHS comes with free dynamic DNS that almost configures itself.

By: Chris

Chris — Sat, 30 May 2009 11:36:23 +0000

DynDNS is what you need.

You can get a free Dynamic DNS hostname (such as jkontherun.dyndns.org) by going to http://www.dyndns.com/. There is a how-to guide that will walk you through the whole process here:

http://www.dyndns.com/services/dns/dyndns/howto.html

By: eTomm

eTomm — Fri, 29 May 2009 23:26:44 +0000

I bought a domain for 7 dollars every year, pointed it to ZoneEdit.com (free service), configured DNS-o-Matic to manage zoneedit, dyndns and no-ip.

To update Dns-o-matic i use a old version of Dyndns updater modded to update dns-o-matic.

And i use OpenDNS as dns servers.

At the end i payed just 7 dollars and i have a true domain pointing to home.