Network Configuration Issues

Active Directory—The head node and each compute node must be members of the same domain before the Compute Cluster Pack is installed.

Firewalls—The Windows Firewall can occasionally prevent nodes from being accessed. This depends on your exact network configuration, so turning the Windows Firewall on or off in the HPC Management Console may help. The firewall setting for the Private and Application network should be turned off.

File Shares—If the compute nodes are isolated on the private network (without direct access to your public network), then all access to a public network file server from compute nodes is through the Network Address Translation (NAT) or Routing and Remote Access on the head node. The file server will see these connections through the NAT as coming from a single node and will therefore allow only one connection at a time. This can cause jobs to fail if multiple compute nodes require access to the same server at the same time. If compute nodes are not on the public network, HP recommends configuring the file share on a node on the private network. This can be the head node, a compute node, or a dedicated file server.