There are probably multiple causes for this problem. I think the most common problem is name resolution due to the network configuration / setup. This is often difficult to diagnose end requires detailed info on the network configuration. Another cause could be a firewall somewhere in your network which is blocking required ports or programs. Some good info which may help you troubleshoot your problem can be found
overhere. When you try the solution which involves disconnecting from the internet please follow the instructions provided in the answer of
this thread.
Please have a look
overhere for an alternative solution if all else fails. Personally I think it's a bit of a hassle however it could provide a solution for you problem.
Although there's more people running into this problem I don't think it appears as often as you suggest. In that case this forum would be flooded with related posts. If you want to draw attention from the home server development team the best thing to do would be to file a bug report on the windows home server connect feedback site, instructions at the bottom of
this page, or find similar feedback items from other users and vote on them.
