Windows Home Server Power Pack 3 resolves OpenDNS issues

This post describes an issue ‘where ISPs adopted OpenDNS and similar services for home network and users started having issues connecting to their Windows Home Server: connector software cannot locate server and its impossible to join new home computer to home server!, and how to resolve those issues in Power Pack 3.’ The root cause […]

This post describes an issue ‘where ISPs adopted OpenDNS and similar services for home network and users started having issues connecting to their Windows Home Server: connector software cannot locate server and its impossible to join new home computer to home server!, and how to resolve those issues in Power Pack 3.’ The root cause is the name resolution solution mechanism of OpenDNS doesn’t work well with whs. When a computer looks for IP, it follows: 1. looks up HOSTS file, if not found, going to step 2. 2. Consults DNS server for the name. If not found, going to step 3. 3. Asks NETBIOS if there’s a name exists in local network. Home server connector depends on step 3, because WHS is located in local network and shouldn’t be resolved by any DNS server. However it never has a chance to go to step 3 because OpenDNS will always respond ”yes” and point to an external IP in step 2. As a result, connector software would try to connect to an external IP, which always results in failure. “In WHS PP3, the problem is addressed and resolved. Solution is simple: connector service running on home computer updates its HOSTS file, adding an entry for WHS in the network. IP address in the entry is what whs announces via UPnP broadcast.”