WHS Built in web server RRS feed

  • General discussion

  • I host a website for my local youth group on my home pc, and recently decided to test WHS on it as the main os, meaning there was a major conflict with the built in web sevrer software. i found it very annoying having to work round it, instead of being able to disable the service and being able to assign port 80 to some other software.


    I suggest either an ability to FULLY disable the service or the ability during install not to have this feature.


    The server hosts both website and now 500+ gig of files for home network sharing as it is easier to have the files in one place, apnd eventually having the printer on it too, which i see is already a diffrent topic.

    Wednesday, November 21, 2007 12:01 PM

All replies

  • Froggy, WHS isn't really designed to be a general-purpose server operating system. Microsoft's expectation is that it will be used as a headless network appliance, and extended through add-ins written using the WHS SDK. You can change the port that the default web site uses, but that web site is also used during the installation of the client software, so doing so may interfere with setting up additional clients. Disabling the service entirely really isn't an option for the same reason.
    Wednesday, November 21, 2007 3:42 PM
  • I am running two additional web sites on my WHS system in addition to the built-in one:


    www.composer.ws and www.nut-house.net


    All use port 80, but I set them up with host headers - very simple, and no conflicts.


    Wednesday, November 21, 2007 8:09 PM
  • I would like to know more about how you did that. It sounds fascinating.
    Monday, November 26, 2007 2:51 PM
  • Does anyone know how to setup host header redirection for https? For example, I would like to have https://www.foo.com direct to my WHS login, but https://www.bar.com redirect to http://www.bar.com.


    Sunday, December 2, 2007 6:28 AM
  • As far as I know, host headers don't work with SSL on IIS.
    Sunday, December 2, 2007 2:20 PM
  • Correct, host headers do not work with SSL. However, you can always assign more IP addresses to your NIC. 


    Most likely your WHS is on your internal network. Disable DHCP on it and assign it multiple static IP addresses (outside the scope of the DHCP address pool of course).  You can then assign different IP addresses to the different sites in IIS.


    On some of my web servers I have 8 different IP addresses assigned to one NIC so that I do not have to use host headers.

    Sunday, December 2, 2007 2:57 PM