Remote-Transport: no TCP keep alive for listening socket

• Related Articles

• zenLogSrv: no TCP keep alive for listening socket

  Description The TCP server of zenLogSrv.exe did not send TCP keep alive messages to check if the TCP connection is still available. The issue has been addressed by automatically enabling TCP server now automatically enables the TCP keep alive for the ...

• In Docker-Compose: no TCP keep alive for listening socket, port 50780

  Description In Docker the TCP server of process zenLogSrv.exe did not send a TCP keep alive to check if the TCP connection is still available. The issue has been addressed by automatically enabling TCP server now automatically enables the TCP keep ...

• Checklist: Service Engine files cannot be transferred via Remote Transport

  Time estimate: 30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• FAQ: How can you bypass the license query on a remote zenon Service Engine version 7.60 or lower when using a zenon Engineering Studio version 8.00 or higher?

  The remote transport verifies if there is license present on the remote machine. Since the license system changed with zenon 8.00 the remote system doesn't recognize the activated (8.00 or higher) license. To bypass the problem it is enough to insert ...

• DNP3_TG driver: network interface configured for UDP listening port / TCP Dual Endoint port, is not taken over

  Summary In the driver configuration of the DNP3_TG driver the network interface that can be configured for the UDP listening port or the TCP Dual Endpoint listening port, is not correctly taken over in the runtime. Instead the driver always opens a ...