I think I figured it out...
It seems like it had to do with routing. I had to manually enter in persistent routes to make sure the servers in question knew how to get to each other.
For example on NOROIT (open command prompt and type)...
route add -p 10.71.1.7 mask 255.255.255.255 10.71.1.1 metric 1
Then on NORCL2N2 type...
route add -p 10.71.1.15 mask 255.255.255.255 10.71.1.1 metric 1
This is a "band aid" solution and something else... something bigger is an issue... I think it might have something to do with the Hyper-V server and the virtual nics...
It seems that even if I added a static route for 10.71.1.0 mask 255.255.255.128 it would not know how to get to the servers... Only after adding each one was I able to get it working.
Update / SOLUTION (this is what fixed the issue):
It was much simpler then I was making it out to be... It seems on the switch that I was using (Dell Layer2) the ports being used by the servers NORCL1N1 and NORCL1N2 were set up on a different VLAN. I thought the ports were damaged on the switch at first but instead somehow there VLANs were changed when I took them out of a LAG (used for teaming). I originally had 3 NICS on NORCL1N1 set up as a team and in turn had 3 ports on the switch set up in a LAG. I turned towards using the NICs on the server WITHOUT teaming involved (due to issues with virtual macs, ip conflicts, etc) and wanted to dedicate a NIC for virtuals, one for cluster-heartbeat, and 1 for the host machine. After doing that and removing the teaming from the server, then removing the LAG from the switch, I thought I was good to go... Not so fast.. I had to go back to each port on the switch and reset the VLAN the ports belonged to again...
Seems everything is fine now! Hope this helps someone out...