Summary
This article describes common error messages encountered when trying to connect the adTempus Console to an adTempus server, or when one adTempus server tries to connect to another (e.g., Master connecting to an Agent)
Symptoms
When you start the adTempus Console and/or try to connect the Console to an adTempus server and the connection cannot be completed, you receive one of the following error messages.
The same messages may be reported by an adTempus server when it fails to connect to another adTempus server, such as when a Master instance tries to connect to an Agent.
The following sections describe common reasons for failure.
No connection could be made because the target machine actively refused it
This message generally indicates that the adTempus service is not running on the target server. Use the Windows Services tool to be sure that the adTempus service has been started. If the service is not running, start it. If the service fails to start, see article K00000222 for troubleshooting information.
This message may also occur if a firewall or other security software is blocking access to the adTempus port (by default, TCP port 3760).
- On the computer where the Console is running, make sure outbound connections to port 3760 are allowed.
- On the computer where the adTempus service is running, make sure inbound connections to port 3760 are allowed.
Connection Testing
The tcping utility can be used to test the connection to the remote server. Download the tool and run it from a command prompt using the following syntax:
tcping computername 3760
Where computername is the name or IP address of the server you're trying to connect to. If tcping 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.
