XCOM SSL ping to Windows server fails with return value 10038

Products

• XCOM Data Transport
• XCOM Data Transport - Windows

Issue/Introduction

Attempting an XCOM SSL (secure) port ping test from a working XCOM for Windows server to another problem server fails with return value 10038 i.e.

"%XCOM_HOME%\xcomtcp" -ping REMOTE_SYSTEM=##.##.#.# PORT=8045 SECURE_SOCKET=YES TRNENCRL_CIPHER=ALL
Copyright (c) 2012 CA.  All rights reserved.
#XCOMN0298E Unable to allocate remote transaction program: Txpi  215: Socket send error return value = 10038

 The unsecure port test is successful.
"%XCOM_HOME%\xcomtcp" -ping REMOTE_SYSTEM=##.##.#.# PORT=8044 SECURE_SOCKET=NO TRNENCRL_CIPHER=ALL
Copyright (c) 2012 CA.  All rights reserved.
XCOMN0882I PING INFO FOR localhost
XCOMN0882I RELEASE=r11.6   SP03 GEN LEVEL 22110    SYSTEM NAME=sys1 SYSTEM ID=w19
XCOMN0882I NEGOTIATED CIPHER=XCOM

A similar error occurs in the opposite direction SSL ping from the problem server to the working server.
Only occurs on one XCOM for Windows server. Many others with an identical configuration have no problem.

Environment

XCOM™ Data Transport® for Windows
AWS is hosting the Windows servers.

Resolution

1. A telnet test from working server to problem server using port 8045 was successful which would seem to indicate no underlying firewall problem.


2. After a xcomtcp secure ping from working server to problem server:
a. The xcom.log on the working (sending) server showed delayed response of 19 seconds:
*****
2024/07/20 10:47:25 TID= PRG=xcomtcp PID=2324 IP=##.##.#.#:8045
XCOMN0813I Secure TCP/IP Connection Requested.

2024/07/20 10:47:44 TID= PRG=xcomtcp PID=2324 IP=##.##.#.#:8045
XCOMN0780E:
*****

b. The xcom.log on the problem (receiving) server showed just:
*****
2024/07/20 10:47:25 TID=REMOTE PRG=xcomtcp PID=7048 IP=##.##.#.#:58046
XCOMN0812I Remote Secure TCP/IP Connection Requested.
*****
Note that here is no later message "XCOMN0818I Secure TCP/IP Connection Ended" which is what should occur when there is a successful ping.


3. A return value of 10038 has previously been reported when there was an issue with the root SSL certificate being incompatible across 2 XCOM machines but for that with the XCOMN0780E message there should also be a "TxpiInitSSL Failed" error message.


The root cause turned out to be some network configuration problem which impacted the packets being sent/received for the SSL ping/connection test.