Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 271
  • Last Modified:

Windows NLB issue after moving virtual server to new host

Hello Everyone.  I had NLB working perfectly between to virtual terminal servers.  However I moved one of the terminal servers to a new host machine (same name and ip addresses) and now I cannot successfully add it to the cluster.  I've even totally removed the cluster and recreated it.  Basically, NLB will configure the nic properly and then complain that it can't find the server.  Also once this happens, you cannot ping the ip address of the server.  This part is even stranger, if I recreate the cluster and add the problem server first, everything is fine but as soon as I add the "good" server, the other fails with the same issue.  NLB almost acts like it storing some old config information and I'm not sure how to remove it.
0
rtmc_jneal
Asked:
rtmc_jneal
  • 2
1 Solution
 
kevinhsiehCommented:
Are you using multicast or unicast? If you are using unicast, do you have 2 vNICs on the VM and enable mac address spoofing on the NICs?

What is your hypervisor?
0
 
rtmc_jnealAuthor Commented:
I did forget to enable spoofing.  This is now enable however still having the same issue.  I'm using unicast with 2 vNICS on Windows 2012 R2.
0
 
kevinhsiehCommented:
Did you enable MAC address spoofing on both VNICs? I know that it is hard to figure out which NIC is which between the hypervisor and guest VM.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now