

Troubleshooting Guide › Troubleshooting and Maintenance Procedures › How to Troubleshoot Connection Problems
How to Troubleshoot Connection Problems
Many factors affect connections between CA ControlMinder computers. Connection problems include being unable to connect to a remote CA ControlMinder computer, or the connection to the remote computer timing out. The following process helps you identify the cause of the connection problem.
Note: For assistance, contact CA Support at http://ca.com/support.
- Check the CA ControlMinder computers for recent changes to the following:
- Encryption key
- Encryption method
- TCP and UDP ports
- Review any new or recently changed rules in the TCP, CONNECT, HOSTNET, or HOST classes.
- Determine the port that has the connection problem.
- Run a trace and review the trace file for:
- Connections that CA ControlMinder blocked due to TCP rules or other rules
- A code other than P (permitted) next to the port number that has the connection problem
- Review the CA ControlMinder audit log for D (deny) records that refer to the problematic port.
- Check that firewalls do not block the problematic port.
- Review the log files for your OS for error messages that are caused by ports that cannot bind.
More information:
Change Port Number for CA ControlMinder Agent Communication
Copyright © 2013 CA Technologies.
All rights reserved.
 
|
|