locked
Two WHS websites running on same network? RRS feed

  • Question

  • How do I get two windows home servers both running their remote access sites to be accessible on the internet using the same, or different domain names. I've tried changing the ports on one of the servers, I've tried turning off remote access on one of the servers and putting a link on the working server to the websites on the second server without a domain name, but for obvious reasons it won't work... it works locally as in //server/remote/logon... blah blah blah.

    So the bottom line is, how do I:

    A: Get two separate domain names working from the same network/IP address

    B: Link the sites together so I can access either server from the internet.

    Thanks for the help!

    Monday, July 12, 2010 6:59 PM

All replies

  • I don't see why port forwarding wouldn't work

    http://myname.homeserver.com:80  -> server1:80

    http://myname.homeserver.com:81 -> server2:80

    Similar process for port 443. I choose port 444 for simplicity.
    Not sure if you can hack the 4125 port for remote access to do the same thing.

    Monday, July 12, 2010 9:08 PM
  • So the bottom line is, how do I:

    A: Get two separate domain names working from the same network/IP address
    B: Link the sites together so I can access either server from the internet

    Allthough technically possible, with Windows Home Server this is not a 'supported' configuration.
    That said I doubt that you could accomplish such a configuaration with WHS unless..

    1) You aquire  two separate IP-addresses (one for each server/domain)
    or
    have a 'router' that is able to do port-forwarding based on http request headers.

    2) You 'hack' the Home Server RA-site of one of the servers to work with non-standard ports (i.e. not port 80 and 443)
    (All though in theory possible, I haven't heard of anyone doing this succesfully - as WHS relies on these portnumbers?)

    - Theo.


    No home server like Home Server
    Monday, July 12, 2010 9:17 PM
    Moderator
  • I've tried that, and everytime I try putting the the port as in "xxxxx.homeserver.com:80" it gives the lovely error "The webpage cannot be displayed, most likely cause: some content or files on this webpage require a program that you don't have installed.

    So I have no idea what the heck I can do, I've even tried connecting IIS 6.0 on WHS to IIS 7 on the "VAIL" Server, but it won't connect.

    Now I'm just confusing myself. -_-

    The webpage cannot be displayed

     
     

    Most likely cause:

    • Some content or files on this webpage require a program that you don't have installed.
     

    What you can try:

     

    Search online for a program you can use to view this web content. <noscript id="noJavascript"></noscript>

     

    Retype the address.

     

    Go back to the previous page.<noscript id="goBack"></noscript>

    Monday, July 12, 2010 9:19 PM
  • Also, I changed the ports in the VAIL server, but I'm not sure I did it correctly. Should I just leave those normal, and change them in the main server?
    Monday, July 12, 2010 9:21 PM
  • Maybe I could get a separate IP... that could be a possibility. Hmm. I'll write back in a few hours, I'll see what I can do. Thanks a lot for the help. I don't know why I didn't think of that. Haha
    Monday, July 12, 2010 9:28 PM
  • Personaly I'd prefer the multiple IP option, but most WHS users (inclusing me :-|) will only have one IP adress available.

    - Theo.


    No home server like Home Server
    Monday, July 12, 2010 9:48 PM
    Moderator
  • The recommended and supported configuration is to have only one Windows Home Server with Remote Access enabled. Connect those PCs you will want to reach from afar to that server, put the data you will want distant access to on that server, and use remote desktop from one of those PCs to your other server if you absolutely have to get to something on it.

    Failing that, the traditional approach is to use a reverse proxy server. Various options are discussed here and here. The second link uses a reverse proxy server; while it discusses Vail, the basic concepts are applicable to V1 as well. Note that there is no supported way to get two servers working at the same time, and anything you do to achieve that is unsupported to one degree or another. Messing about with the Windows Home Server web configuration can leave you with some fairly serious issues if you don't know what you're doing, so please be extremely careful.


    I'm not on the WHS team, I just post a lot. :)
    Monday, July 12, 2010 10:44 PM
    Moderator
  •  On 7/12/2010 4:28 PM, Wingmantyco wrote:

    Maybe I could get a separate IP... that could be a possibility. Hmm. I'll write back in a few hours, I'll see what I can do. Thanks a lot for the help. I don't know why I didn't think of that. Haha

    The Port 80 and Port 443 portion of this can be solved using Evader's method.  As for the domain, you most likely won't be able to register them both at homeserver.com.  What you could do is get a freeweb.com address (or any free website hosting service) and create your landing page there.  Have links to each server, and have them both point to your homeserver.com domain.  Possibly like this:

    Server1 ==> http://mydomain.homeserver.com:80
    Server1 ==> https://mydomain.homeserver.com:443 (https:)

    Server2 ==> http://mydomain.homeserver.com:81
    Server2==> https://mydomain.homserver.com:444 (https:)

    That may do what you want, although I would ask why you want to have two home servers (aside from that you're testing Vail).

    Your other alternative is to get the second IP (and possibly a second modem and router).

    Have a great day:)
    Patrick.


    Smile... Someone out there cares deeply for you.
    Have you updated today?
    http://update.microsoft.com


    Smile.. Someone out there cares deeply for you.
    Wednesday, July 14, 2010 5:58 PM