Windows Server TechCenter >
Windows Server Forums
>
Windows Server 2008 R2 Hyper-V
>
Windows Server 2008 R2 Hyper-V VM NLB unable to connect via RDP using VIP
Windows Server 2008 R2 Hyper-V VM NLB unable to connect via RDP using VIP
- Hi all, I have a weird problem with running nlb on my VMs on W2K8 R2.
The Setup:
Host : Windows Server 2008 R2 with Hyper-V running Hyper-V
Guest OS : Windows Server 2008 SP2 with all the latest patches and updates running as a TS Server
Network : 1 dedicated NIC setup for Virtual Network as External. MAC Spoofing enabled.
I'm trying to setup an NLB cluster inside the VMs, but am encountering a weird problem. I can create and join the VM successfully to the NLB cluster, and NLB Manager reports the VM as being successfully converged. However, if I try to access the VM using RDP via the VIP it always fails. The NLB has port rules that states all traffic on both tcp and udp and for all port ranges.
I can connect to the VM via rdp directly (using its own IP) without any problems. Inside the VM, I can successfully connect to all network resources and the internet without any problems.
I've noticed in R2 that you can't use the old trick used in R1 of setting the VM mac to the static cluster MAC to enable it to join the cluster. Now you must enable MAC spoofing for it to successfully join the NLB Cluster. I've tried dynamic with MAC spoofing, static with MAC spoofing, static set to the NLB Cluster MAC with MAC spoofing, and all of them joins the cluster successfully but still fails if i try to access them via the VIP.
It's very weird and I hope someone can help me :)
Answers
- I think I found the culprit. Originally the NLB cluster was created using VMs from an R1 Hyper-V. I joined an R2 hyper-v vm to that cluster while the R1 was still online then took the R1 offline.
It looks like there's an incompatibility between running R1 hyper-vm and R2 hyper-v vm in the same nlb cluster (possibly due to the different way that hyper-v handles MAC assignment?).
But once I created it using only R2 hyper-v vms using a new VIP, it worked fine.- Marked As Answer byj2 Global Friday, October 23, 2009 4:51 PM
All Replies
Hi,
According to the description, the issue seems to be related to networking. As we mainly focus on the Hyper-V question about Windows Server 2008 R2 system and here is not the best support resource for networking, it is recommend you to get further support in the corresponding community so that you can get the most qualified pool of respondents. Thanks for your understanding.
For your convenience, I have list the related link as followed.
Platform Networking
http://social.technet.microsoft.com/Forums/en-US/winserverPN/threads
Vincent Hu
- I think I found the culprit. Originally the NLB cluster was created using VMs from an R1 Hyper-V. I joined an R2 hyper-v vm to that cluster while the R1 was still online then took the R1 offline.
It looks like there's an incompatibility between running R1 hyper-vm and R2 hyper-v vm in the same nlb cluster (possibly due to the different way that hyper-v handles MAC assignment?).
But once I created it using only R2 hyper-v vms using a new VIP, it worked fine.- Marked As Answer byj2 Global Friday, October 23, 2009 4:51 PM
