locked
Do you need to purchase a domain with WHS software? RRS feed

  • Question

  • Maybe this question seems stupid but back in april of this year when I applied for the WHS beta and started testing. I thought when setting up livenode.com ( which is now homeserver.com) that I actually needed to purchase a domain ex: mikeesc380.??? from a register to get access to my WHS. When going through the remote access setup I thought it required an actual domain name. (something.???) Now I'm thinking not so and have been told by a qualified MVP that I was wrong. I found a message about using my domain name in stead of the livenode.com that suggested uninstalling that portion of the remote setup and leaving it blank. And it did work! I could type in my domain (mikesc380.???) and access my site but with security errors. I have also went as far as puchasing a cox business account for a static ip that has an open port 80, thinking Cox was causing the security error by them blocking port 80 on my home account in my early testing. Now after actully purchasing WHS OEM 32-bit. I have found that if I use the domain name that I registered I still get the security error. But after setting up remote access with my domain name + homeserver.com I no longer get security error.

     So when setting up remote access and going through setup and when asked for domain name do you need a registered Domain or not? Miss interpretationon on my part from documentation with WHS beta possibly. Just trying to clarify. For myself and maybe others.

    And if your ISP blocks port 80 for a home user account will you still get a security error if they block port 80? 

    Another words if I type mikesc380 when asked for domain in remote setup instead of mikesc380.??? will it work?

    mikesc380

    Saturday, December 8, 2007 1:53 AM

Answers

  • Depending on who made your home server, your choices for a domain name are kind of limited... OEM machines for instance out of the box only have free support for homeserver.com (and livenode.com if you registered it during the beta)

    Outside of the free options... you are free to buy a name of your own (mikesc380andhishomeserver.com for instance)... however you would be responsible for managing the DNS records yourself.

     

    As for the certificate errors... they really only occur in one of two cases:

     

    1. You connect using a certificate that is not signed by a trusted root authority (the default state without the latest update)
    2. You connect using a domain name (like a stand alone dynamic DNS service outside of WHS’s control) that the certificate doesn’t cover.

     

    Regarding port 80... it’s biggest function is simply to redirect you from the http site (port 80) to the https (port 443) one... so instead of typing out http://yourname.homeserver.com... use https://yourname.homeserver.com instead.

    Saturday, December 8, 2007 3:06 AM
    Moderator

All replies

  • The IE access security issue should have been resolved by the recent update

    Have you applied this yet?

     

    Saturday, December 8, 2007 2:43 AM
  • Depending on who made your home server, your choices for a domain name are kind of limited... OEM machines for instance out of the box only have free support for homeserver.com (and livenode.com if you registered it during the beta)

    Outside of the free options... you are free to buy a name of your own (mikesc380andhishomeserver.com for instance)... however you would be responsible for managing the DNS records yourself.

     

    As for the certificate errors... they really only occur in one of two cases:

     

    1. You connect using a certificate that is not signed by a trusted root authority (the default state without the latest update)
    2. You connect using a domain name (like a stand alone dynamic DNS service outside of WHS’s control) that the certificate doesn’t cover.

     

    Regarding port 80... it’s biggest function is simply to redirect you from the http site (port 80) to the https (port 443) one... so instead of typing out http://yourname.homeserver.com... use https://yourname.homeserver.com instead.

    Saturday, December 8, 2007 3:06 AM
    Moderator
  • Not in my environment with exceptions. Weather beta or full 32-bit OEM. If I use user+homeserver.com your right! security does not come up. But if I try and use actual Domain name which I'm finding I did not need to Purchase with WHS (The Beauty of it) I'm finding out. I get security error with RED Bar allert! in IE7. Which I always got in beta WHS  using actual Domain name or livenode name.

    Now I only get  security error when using domain name. I can continue on as you always did in beta or before the fix (update) and still access all files but why not use your own Domain if you can. Wouldn't that be less hops and more direct to your server. See the reason why I got static was ISP blocks port 80. I'm worried ISP's will start blocking not just port 80 but 443 also because of bandwith or security. After all they (ISP's) don't want or like homeuser's to do this because of bandwith or security issues. Or is 443 the Key SSL? Again I could be lost in what Microsoft is doing as I'm a show me self taught person.

    mikesc380

     

     

    Saturday, December 8, 2007 3:26 AM
  • So if I Call cox I need to tell them to add a PTR to my domain for homeserver or would I use a cname can't remember?

    mikesc380

     

    Saturday, December 8, 2007 3:32 AM
  • Port 443 is the default port for SSL over HTTP and while it is possible that your ISP (or any other) will block 80, 443 and any others used by WHS... that risk unfortunately exists for just about any port you will try to use. At times the best thing to do is not give them reason to block it... such as not letting friends download lots of high bandwidth content from your home server.

     

    I cannot say if COX would be the ones to talk to about a PTR record for your domain... instead I’d suggest just sticking with a... mikesc380.homeserver.com like domain name, it’s free, it’s easy, and it automatically updates whenever the IP address of your home server (or as it is viewed by the outside world) changes... largely removing the need for a static IP address.

    Saturday, December 8, 2007 4:14 AM
    Moderator
  • Cox blocks TCP Port 80 inbound for residential accounts...

     

    http://tinyurl.com/3dwztm

     

    I am on Cox HSI and access my WHS via TCP Port 443 (ie. https: address) and TCP Port 4125 with no problems using the homeserver.com FQDN. I also have a SSH server on my WHS listening on a high number port, ie. 40000+, for emergency access via Remote Desktop.

    Saturday, December 8, 2007 12:32 PM