Symptoms
In the Remote Agents view in the adTempus Console, adTempus may show the status of an Agent as "Not connected" even though the Agent is actually connected.
More Information
If there is a problem with the Agent connection, the status generally will include an error message after "Not connected." For example: "Not connected: No connection could be made because the target machine actively refused it."
If no error message is present, you can generally assume that the Agent is really connected.
This problem only affects reporting of the Agent status in the Console. The Master server knows the correct connection status, and will send jobs to the Agent even if the Console is reporting "Not connected."
If the Agent really is not connected, jobs will not be sent to the Agent.
