Problem with NLB cluster within Virtual server using Hyper-V.

Here is our setup:

2 Server 2008 Standard host machines using Hyper-V.  Each host has 2 guest machines.  Each host has 6 network adapters (2 allocated for the host machine, 2 for guest 1, and 2 for guest 2)
Host 1 - Guest 1A and Guest 1B
Host 2 - Guest 2A and Guest 2B
IP address detail:
Host 1:       10.0.0.5 (dedicated) and 10.0.0.6 (used for NLB cluster)
Guest 1A:  10.0.0.7 (dedicated) and 10.0.0.8 (used for NLB cluster)
Guest 1B:  10.0.0.9 (dedicated) and 10.0.0.10 (used for NLB cluster)

Host 2:       10.0.0.11 (dedicated) and 10.0.0.12 (used for NLB cluster)
Guest 2A:  10.0.0.13 (dedicated) and 10.0.0.14 (used for NLB cluster)
Guest 2B:  10.0.0.15 (dedicated) and 10.0.0.16 (used for NLB cluster)

Cluster IP address:
For Host 1 and 2:           10.0.0.17
For Guest 1A and 2A:   10.0.0.18
For Guest 1B and 2B:    10.0.0.19


We have Host 1 and 2 setup for NLB and it's working perfectly.  We have Guest 1B and 2B setup on another NLB cluster and they are working perfectly.  I am having an issue with Guest 1A and 2A's NLB cluster.  After configuring the cluster, it says converged and I can ping 10.0.0.18 and can ping 10.0.0.14 with no problem.  When I ping the IP address of the network connection set as the NLB connection on Guest 1A (10.0.0.8) I get nothing, it times out on me everytime.  Yes, I have done the "trick" with setting the MAC address of the NLB cluster on the virtual server's settings for the network adapter within Hyper-V.  I have tried just about everything from removing/re-adding the network adapters for that server, even uninstalling/reinstalling them on the host machine and then redid all the configuration correctly.
 
One thing that is weird is that I'm able to ping the network adapters with no problem up until I add it to the NLB cluster.  After shutting down the server, changing the setting for the MAC address and then rebooting the server, and the NLB says converged.  I go into the Network connections of 10.0.0.8 and it says "Unidentified Network" for that adapter (all of the others have our domain name listed there).  Everytime I try to redo all the configurations, it always come back with "Unidentified Network".  It works perfectly for the other virtual servers (1B and 2B) so why is it causing a problem with the other.

Does anyone know what the problem is here?
Is there a way to clear the network stack or something?

Any help with be greatly apprecitated!