I thought I had posted this, but the system appears to have eaten it. I will try again.
I am setting up a 2-node Server 2012 Failover Cluster. I have installed the tools on each server, and I have shared storage waiting in the form of a Dell Compellent 8000 system. Each of the 2 nodes has 4 NICs: #1 is External (they are both on the same public subnet, and can ping each other successfully), #2 is Internal (a private gigabit switch intended for the heartbeat, they are 10.0.0.101 and 10.0.0.102 on a 255.255.0.0 network and can ping each other), #3 and #4 are iSCSI switches that are part of the Compellent System.
When I run the Failover Cluster Manager > Validate Configuration Wizard, and enter the same of the first node (The one I'm running it on), that's fine. When I enter the second node, it says "The node cannot be contacted. Ensure that the node is powered on and is connected to the network."
Obviously it is, as I can ping between them on both external and internal connections. I also tested by creating a share on CL-01 (Node 1) and was able to access it via UNC path on Node 2.
Both servers are in our Active DIrectory, and when I Browse through the Validate Wizard, both servers appear in the OU.
Is there something I may be missing? Can you tell me what port(s) this wizard may be using to communicate so that I can verify they're not being blocked somehow? It should not be the case, but I am at a loss to explain why these nodes can communicate in every sense except that one.