Today i deployed a NLB cluster on a window server 2008 R2 them are some VMS running on hyper-v R2 base on windows server2008R2 to achieve Network balance and fault tolerance for a certain production works with IIS.

        I prepared 2 NICS on each NLB node VM server  and planed to launch a NLB cluster work in unicast mode. Everything

is ready. But unlucky accident is always happened when we are enjoying every procedue  which processed as sucessful as our p_w_picpath. It is not a exception for the case. Yes, like some novel it contains involved  plot.

        Ok, long story to short. The problem message told me some message that cluster ip information and the dedicated ip imformation can't configure in TCP/IP  property and with a error code (sorry, forget to save the code).

      Finally i foud a solution work around the issue. In fact , it is very simple ,just open MAC spoofing feature at VM setting of hyper-v Of windows server 2008. The same problme had not encountered in version windows server 2008 RTM.

   The following is interesting document about MAC spoofing of hyper-V r2.

http://blogs.technet.com/b/jhoward/archive/2008/07/15/hyper-v-mac-address-allocation-and-apparent-network-issues-mac-collisions-can-cause.aspx

http://blogs.technet.com/b/jhoward/archive/2009/05/21/new-in-hyper-v-windows-server-2008-r2-part-2-mac-spoofing.aspx