A ticket was recently opened for this issue. It turned out that the problem was caused by a difference in the Network configurations between the two nodes. One node had two DNS servers configured and the other only had one, which happened not to be running. When they started the cluster they were not able to create session recordings. This in turn prevented them from connecting to their target systems, as the recording configuration was set for Security Safe. When they realized the DNS server was down, they added the second DNS server to the Network configuration. After doing this and Restarting the Network and the cluster recording worked. Keep this in mind if you run into this problem.