Why does the Network Load Balancing (NLB) configuration on Windows Server R2 always error "host unreachable"?

Configuring Windows-based Network Load Balancing is easy, the operation is very simple, the mouse can basically complete the point, but in the process of node (real server) operation sometimes encountered some host inaccessible error message. Why is this?

Figure 1 Configure NLB on one of the nodes after the update is an error once, let people use very not practical

The error will appear in the description "host is inaccessible." Error connecting to "xxx hostname".

In Windows and host name related to some network settings have DNS resolution, WINS resolution, the local HOSTS file parsing these kinds.

Because there is no intranet DNS and WINS server in the environment, the younger brother tried to write the "xxx hostname" and the IP relationship to the local hosts file to see if this problem can be resolved.

After writing the host name and IP correspondence to the local Hosts file, refresh the Load Balancer Configuration window again to resolve the problem.

Now review the previous configuration, the younger brother uses the IP address directly fill in, add Host to the cluster dialog box, and later operations need host name interoperability, because write and read each other node through the SMB protocol to pass information, this is the cause of the error during the refresh process.

This issue is now resolved through the Hosts file.

-=eob=-

Why does the Network Load Balancing (NLB) configuration on Windows Server R2 always error "host unreachable"?