adTempus Connection Failure Troubleshooting

When the connection fails between the Console and server or between two adTempus server instances (e.g., Controller connecting to an Agent), one of the following errors may be reported:

  • A connection could not be made to the adTempus server: No connection could be made because the target machine actively refused it (ADT000066E)
  • A connection could not be made to the adTempus server: [reason] (ADT000066E)
  • The target server "computername" could not be found or the adTempus service is not running on the target computer.

These messages indicates that the adTempus Console cannot find the target computer, or that adTempus is not running on that computer. Possible causes include:

  • The adTempus service is not running on the target computer. Check to see if the service is running, and start it if necessary. If the service fails to start, see Service Startup Troubleshooting.
  • You have entered the name or address of the target computer incorrectly, or the wrong instance name. Double-check this because it happens more often that you think.
  • The network connection between the two computers has failed.
  • Access to the port on which the adTempus server listens for connections is being blocked by a firewall or proxy server. See Port Information.

Connection Testing

The PowerShell test-netconnection applet can be used to test the connection to the remote server using the following syntax:

test-netconnection -computername computername -port 3760

Where computername is the name or IP address of the server you're trying to connect to. If this succeeds, adTempus should be able to make the connection. If it fails, either adTempus isn't running on the server or something is blocking the connection.