# Troubleshoot policy installation failure due to connection timeouts

Resolve problems when policy installation fails because the connection between the engine and the Management Server times out.

##

The engine is up and running, but policy installation fails when the Management Server is contacting the nodes. When node-initiated contact is active, the Management Server might also wait for contact from a node, but the contact never happens.

The connection might time out for the following reasons:

- There is no network-level connectivity.
- The engine or the Management Server uses the wrong IP address.
- The engine and the Management Server reject each others’ certificates.

For more details about the product and how to configure features, click Help or press F1.

## Steps

1. Check for network problems, such as faulty or loose cables, mismatching speed/duplex settings, IP addresses, and routing.
2. Check the Locations and Contact Addresses of the SMC components, which are required if NAT is applied to these system communications.
3. In a cluster, all nodes that the Management Server tries to contact must be reachable and operational to install a policy on any of the clustered engines. If you have taken down an engine for maintenance, temporarily disable it to install the policy on the other cluster members.
4. If the problem seems to be related to certificates, you can recertify the engine to re-establish contact between the engine and the SMC.
5. Check the engine software version (shown in the Info pane when you select the element in the SMC Client). See the Release Notes for information regarding version compatibility between the engine and SMC software versions.