Automation Point Remote Viewer fails to connect from remote client

Products

Automation Point

Issue/Introduction

Have configured Automation Point (AP) to use Remote Viewer with no security to test but cannot connect to the Remote Manager using a remote client. Receive message:
AXC2110E Remote Manager on hostname is not running

The connection is successful when running Remote Viewer from the AP Server machine and the expected "AP Msg Call" Window is displayed.
Do any other ports need to be open within the network and firewalls besides 5500?

Resolution

1. Per the article What are the ports used by CA Automation Point?, only port 5500 should need to be opened on the AP Server for the remote client AP Remote Viewer to have a successful connection to the AP Server Remote Manager.

2. Support tested in-house and initially received the same failed connection on the remote client.
On the AP Server, Support had to use the Windows Defender Firewall "Advanced Settings" to add an Inbound rule for TCP port 5500 (all remote ports).
That resolved the connection problem and the expected "AP Msg Call" Window was then displayed.

The Windows Defender Firewall change also resolved the reported problem.

Additional Information

To test that the firewall is open to the AP Server port 5500, the Windows Telnet Client can be used from a command prompt on the client machine. Only if the firewall is open for AP Server port 5000 will a telnet connection to it be successful.
The Windows Telnet Client feature can be enabled under "Control Panel\Programs and Features" and then use "Turn Windows Features on or off".

Run the telnet command using either the AP Server IP address or its DNS resolvable hostname i.e.
telnet AP_Server_hostname 5500
a. If the telnet connection is successful the command prompt will clear and then need to use key sequence 'CTRL ]' to get this text displayed:
===
Welcome to Microsoft Telnet Client

Escape Character is 'CTRL+]'

Microsoft Telnet>
===
Then use q to quit.
b. If the telnet connection does not complete then this error will be received when it times out:
Connecting To AP_server_hostname...Could not open connection to the host, on port 5500: Connect failed

2nd occurence

A second occurrence of this type of problem has been reported for only one AP Server SERVER5. The user seeing various problems using Remote Viewer to SERVER5 from a remote client. Using Remote Viewer on SERVER5 itself does not have any problem.
The "CA-AP Remote Manager" service on SERVER5 is running on default port 5500.

Remote Viewer on another AP Server to SERVER5 shows "AXC2110E Remote Manager on hostname is not running"
Running 'telnet SERVER5 5500' on that other server also failed indicating firewall problem per above.

Remote Viewer on laptop to SERVER5 shows connect and then disconnect 140 seconds later.
No 2nd dialog 'AP Msg Recall' is opened after the connect.

Support checked various log files:
1. apDiag Logs from the SERVER5 server.
The Remote Manager axcmgrip.out logs only shows a Remote connection from the local server SERVER5 itself and not from the laptop e.g.
10:40:58.714 S0 P2536 T5540 C=NA Task=22 MGR LISTEN: (mgr_open_remote,3400,I) Remote host SERVER5.www.xxx.yyy.zzz connecting
Thus although the Remote Viewer on the laptop is showing as connected it does not seem to be getting as far as the Remote Manager itself and it must just be connected at some base TCP/IP socket layer. That lines up with not seeing the 2nd dialog for 'AP Msg Recall' being opened and the 140 seconds before disconnect is probably a socket timeout at the laptop end because it is not getting the expected response.

2. Laptop AP Logs
The apview.out and older apview.out.* logs show a "Lost Connection -113" error as well as the "reason:network error" seen in the Remote Viewer:
*****
12:29:40.953 S5 P59556 T60532 C=NA Task=21 WINDOW MANAGER: (rem_open,1,I) AXC2101I Connecting to server5.www.xxx.yyy.zzz 'AP Msg Recall'
12:29:40.959 S5 P59556 T60532 C=NA Task=21 REM_server5.www.x.:AP Msg Rec: (ipq_open_tcp,2000,E) IpqInit: Unable to load WinSock DLL 'ca2_32.dll'; rc:12612:32:02.241 S5 P59556 T21592 C=NA Task=16 REM_server5.www.x.:AP Msg Rec: (snd,103,5000,W) Lost Connection -113
12:32:02.241 S5 P59556 T21592 C=NA Task=16 REM_server5.www.x.:AP Msg Rec: (snd,103,1,I) AXC2102I Disconnect from server5.www.xxx.yyy.zzz 'AP Msg Recall' reason:network error
12:40:59.127 S5 P59556 T62884 C=NA Task=14 WINDOW MANAGER: (rem_open,5,I) Connect server5.www.xxx.yyy.zzz 'AP Msg Recall'
12:40:59.127 S5 P59556 T62884 C=NA Task=14 WINDOW MANAGER: (rem_open,1,I) AXC2101I Connecting to server5.www.xxx.yyy.zzz 'AP Msg Recall'
12:43:18.089 S5 P59556 T63236 C=NA Task=7 REM_server5.www.x.:AP Msg Rec: (snd,103,5000,W) Lost Connection -113
12:43:18.089 S5 P59556 T63236 C=NA Task=7 REM_server5.www.x.:AP Msg Rec: (snd,103,1,I) AXC2102I Disconnect from server5.www.xxx.yyy.zzz 'AP Msg Recall' reason:network error
*****

Also running this netstat command on the server also showed no LISTENING sockets which is not expected: netstat -na | findstr 5500

After Wintel team opened Windows Defender firewall for incoming/outgoing ports 5500 initially still had issues after first reboot, but then a second server restart resolved the problems. The above netstat output also then showed the expected LISTENING sockets:
TCP 0.0.0.0:5500 0.0.0.0:0 LISTENING
TCP [::]:5500 [::]:0 LISTENING