om_tcp not working

#1 Ashok Biradhar

I've configured the NxLog for forwarding the security event logs from windows using the om_udp module and it is working as I can see those logs on the destination AWS EC2(rsyslog) instance. But when I tried to tweak the NxLog configuration for tcp forwarding using the om_tcp, it is throwing an error as shown below: "ERROR couldn't connect to tcp socket on <REDACTED>; A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond." Can someone assist here to overcome this error. FYI, both UDP and TCP reception rules are in place.

#2 gahorvath

Can you verify if it is possible to establish a TCP connection from the system running nxlog to the TCP receiver?

Something like netcat can give you a quick answer to whether it's reachable over TCP on the given port.

The error message indicates there was no response to the initial SYN packet om_tcp sent out, as if a very taciturn firewall ate the packets.