Respond to Command Failed or Connect Timed out errors

There are several possible causes and solutions when to command an engine using the Management Client and receive an error.


  1. Make sure that there is connectivity between the Management Server and the engine.
    The most common connectivity problems include traffic filtering by an intermediate firewall and incorrectly configured NAT configuration. When NAT is configured incorrectly, a required NAT rule for the connection is missing, or the engine’s contact address is missing. The engine sends its status reports through the Log Server, so a green operating status does not guarantee that the Management Server can reach the engine.
  2. Try to refresh the engine’s policy. Read all messages displayed and make sure that none of the nodes perform a rollback to the previous policy. If policy installation fails, see Troubleshooting Policy Installation.