Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Two Windows Home Servers, one client PC RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I have two Windows Home Servers, but can't figure out how to get the Connector software to connect to the second one so I can check stats, change options, etc.

    Didn't find out from other threads how to accomplish this. Did I goof up by getting two?

    Odi
    Odi - Xceed.com - Premier WPF DataGrid
    Wednesday, October 14, 2009 1:54 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    The connector software can only connect to one Home Server. If you want to manage the other server you can:

    1. install the connector on another client, select the second server during installation
    2. on the current client run discovery.exe from C:\Program Files\Windows Home Server to connect to the second server
    3. use remote desktop to connect to the second server (username=adminstrator, password=WHS console password)
    Wednesday, October 14, 2009 10:32 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm certain you won't find a workaround for this. The name doesn't have anything to do with connnecting your clients to the WHS. It's most likely that your WHS has a unique identifier for tying you clients to it. Browsing network shares does work because that is using DNS. At least you know your DNS works.
    Wednesday, January 13, 2010 2:03 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    The connector software can only connect to one Home Server. If you want to manage the other server you can:

    1. install the connector on another client, select the second server during installation
    2. on the current client run discovery.exe from C:\Program Files\Windows Home Server to connect to the second server
    3. use remote desktop to connect to the second server (username=adminstrator, password=WHS console password)
    Wednesday, October 14, 2009 10:32 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    You could also enable Remote Access without configuring a domain and use the web interface (http://yourservername)  to access the console.

    Best greetings from Germany
    Olaf
    Wednesday, October 14, 2009 12:32 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    You could also enable Remote Access without configuring a domain and use the web interface (http://yourservername)  to access the console.
    Note that, should this user be using UPnP for router configuration, this would not work very well, as the two servers (I assume they're in the same physical location) would fight over the web ports and remote access would be, umm, "unreliable". :)

    I prefer kariya21's first answer overall if it's an option, the second one for two servers in different locations with an infrequent need to switch between them, and the third solution if the two servers are in the same location and/or the user is switching between them frequently (like a couple of times a day).
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, October 14, 2009 2:39 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for your answers, very appreciated. Will mark the good ones as helpful shortly.

    Ken, I can't seem to find kariya21's answer -- where or what was it? You prefer it, but I don't know what it is!

    Thanks,
    Odi
    Odi - Xceed.com - Premier WPF DataGrid
    Wednesday, October 14, 2009 5:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Seems Ken was refering to brubbers answer.
    Best greetings from Germany
    Olaf
    Wednesday, October 14, 2009 6:36 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    What Olaf said. I was being distracted when I typed... :P
    I'm not on the WHS team, I just post a lot. :)
    Thursday, October 15, 2009 4:44 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have two WHS boxes in two different locations. I tried to trick my laptop, which I take between the two locations, by giving the server the same name at both sites. This works fine for file sharing, and I do not have to reset the media folders for Media Center when I change spots. But even though the machines have the same names in both locations, Backup will not recognize the client until I run discovery.exe in the second location. Being extremely lazy and overly fond of automation, I am trying to discover a way around this. I would like each WHS to pick up on backups where it last left off without making me run discovery.exe again. Any thoughts on how this can be achieved?
    Wednesday, January 13, 2010 7:49 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm certain you won't find a workaround for this. The name doesn't have anything to do with connnecting your clients to the WHS. It's most likely that your WHS has a unique identifier for tying you clients to it. Browsing network shares does work because that is using DNS. At least you know your DNS works.
    Wednesday, January 13, 2010 2:03 PM