This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.
No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release.
Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect the computer.
You cannot connect to a computer that is running Windows Home Server.
This issue can occur if the Windows Home Server-based computer is on a different subnet than the computer that you are using. By default, a Windows Home Server-based computer is configured to accept connection requests only from computers that are on the same subnet.
Important These steps may increase your security risk. These steps may also make the computer or the network more vulnerable to attack by malicious users or by malicious software such as viruses. We recommend the process that this article describes to enable programs to operate as they are designed to or to implement specific program capabilities. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you decide to implement this process, take any appropriate additional steps to help protect the system. We recommend that you use this process only if you really require this process.
To resolve this issue, configure the Windows Home Server-based computer to accept connections from computers that are on a different subnet. To do this, follow these steps:
Click Start, click Run, type Firewall.cpl, and then click OK.
On the Exception tab, click Remote Desktop, and then click Edit.
In the "Edit a Service" window, click Change scope.
Click Any computer or Custom list. Then, click OK two times.
Note If you select Custom list, type the subnet number or the IP address for the client computers.
Of the three options in the list of scope settings, the My Network (subnet) only option is the more secure setting. This setting does not allow computers that are on a different subnet to connect to the Windows Home Server-based computer.
If you select Any computer, the firewall is open to connections from the Internet. This is the least secure setting.
On the Exception tab, click Windows Home Server Transport Service. Then, click Edit.
Repeat step 3 and step 4 for the Windows Home Server Transport Service service.
On the Exception tab, click Windows Home Server Computer Backup, and then click Edit.
Repeat step 3 and step 4 for the Windows Home Server Computer Backup service.
Try again to connect to the Windows Home Server-based computer.
This behavior is by design.
Typically, all the computers in a home network environment are on the same subnet. When all the computers are on the same subnet, you do not experience the issue that is described in the "Symptoms" section.