Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Using WHS with multiple subnets RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi everyone,

     

    I was told that multiple subnets is not a supported scenario, but I was also told that it should work, as long as the proper firewall settings are in place. Here is what I did so far:

    - changed firewall settings for Remote Desktop, WHS Computer Backed, WHS Transport Service to accept connections from "Any computer"

    - verified that I can telnet from my client computer to my WHS computer, on port 1138 (WHS Transport Service; before enabling the firewall exception, no connection could be made, so that indicated to me that the firewall settings are already in place)

    - pinged my WHS computer from my client, and that worked just fine, because although the client and server are on different subnets, the network is properly setup so things work fine (this is basic stuff, I should probably not even mention it)

     

    An attempt to install the WHS Connector on my client machine fails to autodetect the server (that's fine, since the name is not SERVER), but even the manual detection fails, with this message: "This operation cannot be completed at this time. Please try again later. If the problem persists, please contact WHS support".

     

    There are 2 differences that I think matter, between my client that is working and this new one that does not:

    - the one that is working uses WinXP/x86, the one that does not work uses Win2K3/x86

    - the one that is working is in the same subnet, the one that does not is in a different subnet

     

    What other things I can try to make my scenario work?

     

    Thanks for the help!

    Tuesday, November 27, 2007 10:18 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I changed the firewall settings for UPnP but that still did not help. Then I changed all the firewall exceptions, except the ones for Windows Media Connect, to "any", and immediately WHS Connector was happy Wink

     

    By repeatedly trying various settings, I found out that only one firewall exception is needed for the connector to discover the server (enabling the next step, which is asking for the password). That exception is for HTTP at port 55000. After entering the password the connector gave a much more helpful message, saying that it cannot connect because of, among other things, the firewall settings.

     

    So thank you for your help, I can now back up my systems from their various places in the building!

     

    Here is what I think can be improved so that such scenarios are smother to deal with:

    - have this post updated: http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=1381374&SiteID=50. It does a nice job explaining where changes need to be made, but, at least for me, just changing the settings for only those 3 settings (Remote Desktop Connection, Windows Home Server Backup Service, Windows Home Server Transport Service ) was not enough

    - change the message that is displayed when manual discovery fails to say pretty much the same thing that is displayed when the connector fails after the password is entered (something like proxy, firewall, or other settings are incorrect)

     

    Thanks again for the help!

    Thursday, November 29, 2007 7:42 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    If you move the home computer that is not connecting into the same subnet, does it connect to your Windows Home Server?

     

    Make sure your date and time is correct on the home computer that is not connecting.  Also, make sure the date and time is correct on your home server.

     

    You should be able to connect to your home server using the Manual find options with the firewall ports set to Any Computer.

     

    Tuesday, November 27, 2007 10:29 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    I verified the date and time on both the client and the server and they are all correct.

    Firewall exceptions scope is "Any computer" for Remote Desktop, WHS Computer Backed, WHS Transport Service.

     

    I don't control how IP addresses are assigned, to there is very little I can do to have the client and the server is the same subnet. I'll try to set up a couple more machines in the building, hoping to get the same subnet, just to see if that's the only problem I'm facing.

    Thursday, November 29, 2007 12:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You also need to set both settings for UPnP to Any as well...

     

    Thursday, November 29, 2007 1:17 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    I changed the firewall settings for UPnP but that still did not help. Then I changed all the firewall exceptions, except the ones for Windows Media Connect, to "any", and immediately WHS Connector was happy Wink

     

    By repeatedly trying various settings, I found out that only one firewall exception is needed for the connector to discover the server (enabling the next step, which is asking for the password). That exception is for HTTP at port 55000. After entering the password the connector gave a much more helpful message, saying that it cannot connect because of, among other things, the firewall settings.

     

    So thank you for your help, I can now back up my systems from their various places in the building!

     

    Here is what I think can be improved so that such scenarios are smother to deal with:

    - have this post updated: http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=1381374&SiteID=50. It does a nice job explaining where changes need to be made, but, at least for me, just changing the settings for only those 3 settings (Remote Desktop Connection, Windows Home Server Backup Service, Windows Home Server Transport Service ) was not enough

    - change the message that is displayed when manual discovery fails to say pretty much the same thing that is displayed when the connector fails after the password is entered (something like proxy, firewall, or other settings are incorrect)

     

    Thanks again for the help!

    Thursday, November 29, 2007 7:42 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am having similar problems.  My WHS is on a different subnet from its clients.  But additionally, the subnets are managed by a router, SmoothWall Express.  I'm not sure, but it could be I need to open ports in the router to allow the client to make queries outside of its subnet. 

    Changing the firewall settings scope for the three services described above and in the FAQs allowed Remote Access, but my Windows Home Server Connector software still can't find the server.  I've even tried lowering the firewall completely and so I don't think the firewall on WHS is the issue.  It could be I need the port numbers to apply in the router, but Remote Desktop, WHS Computer Backed, WHS Transport Service do not show port numbers in the firewall settings.  I have opened up the UPnP ports and port 55000, but that didn't help.

    Is anyone aware of all the ports involved for the Connector?  Could someone summarize what needs to be done to allow WHS Connector to make it through a subnetting router?
    Monday, December 15, 2008 6:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    You also need to HTTPS on port 56000

    Regards,

    Darren
    Wednesday, April 29, 2009 5:46 PM