Troubleshooting CO-tsend

The most common reasons for failure are as follows: 

• A firewall, port blocker, or filtering router does not permit communication between the CO-tsend.exe and CO-trecv.exe programs via the configured port number; by default the TCP port 51462. You should check the firewall configuration, or use the telnet command to verify that the CO-trecv.exe program is reachable from the CO-tsend.exe program. It would help if you also verified that no port blocking software (such as found in many common Virus protection programs) is preventing communication between the two programs.
• The CO-tsend.exe and CO-trecv.exe programs are not executing. You should verify via the Windows Task Manager that these programs are running. If these programs fail to start, you should check the respective error logs, either the CO-tsend.log or CO-trecv.log files (located in the same folder as the executable programs).
• The CO-tsend.exe program does not have the DestinationAddress correctly configured. This might be difficult to detect. Double-check the IP address by pinging the DestinationAddress node, or use the telnet command to access the CO-trecv.exe program.
• The CO-tsend.exe program and CO-trecv.exe program do not have the same EncryptKey value. If the CO-tsend.exe program sends a message with the wrong encryption key, this causes an authentication error message to be logged at the main BMC Defender console. Check the BMC Defender messages screen to see if such authentication errors are occurring.

As a final way of verifying operation, set the LogLocal directives of both the CO-tsend.cnf and CO-trecv.cnf files to be True, and try issuing syslog messages via the sendlog.exe utility. You can check the log files of the programs to see if the message reaches the CO-tsend.exe program, the CO-trecv.exe program, or neither.