<![CDATA[Forward event to another NetXMS server is not working]]>Hi,
I have two Netxms Servers with identical events and rules configuration and I want forward events from one to another server.

Both server are installed on the Win7 system and it's connected on the switch in one VLAN.
On the both server firewall is turned off.

I've set the following settings - EnableISCListener and ReceiveForwardedEvents to destination server and restarted the core. On the main server I have created new action type "forward event" with IP address 172.19.228.42 of slave server and I have created rules for some event with forward action.
After alert have occurred on the main server it has nothing sent to slave server. I have check log file on the main server and there is following log
[27-Dec-2016 14:54:25.114] [DEBUG] *actions* Executing action 1 (ForwardEventTo_172.19.228.42) of type FORWARD EVENT
[27-Dec-2016 14:54:25.114] [DEBUG] *actions* Forwarding event to "172.19.228.42"
[27-Dec-2016 14:54:30.121] [WARN ] Failed to forward event to server 172.19.228.42: Connect failed
 
I have run wireshark on the main sever but nothing is receiving the data on port 4702.

Any ideas is there something I've missed?

Tomislav

]]>https://forum.netxms.org/topic/4846/forward-event-to-another-netxms-server-is-not-workingRSS for NodeFri, 13 Nov 2026 19:40:23 GMTWed, 28 Dec 2016 09:29:06 GMT60<![CDATA[Reply to Forward event to another NetXMS server is not working on Thu, 29 Dec 2016 09:03:37 GMT]]>Thanks Victor,

Best regards,
Tomislav

]]>https://forum.netxms.org/post/21564https://forum.netxms.org/post/21564Thu, 29 Dec 2016 09:03:37 GMT<![CDATA[Reply to Forward event to another NetXMS server is not working on Thu, 29 Dec 2016 08:47:45 GMT]]>Hi,

it's already fixed in version 2.1-M1. This fix is also included into upcoming 2.0.8 patch release.

Best regards,
Victor

]]>https://forum.netxms.org/post/21563https://forum.netxms.org/post/21563Thu, 29 Dec 2016 08:47:45 GMT<![CDATA[Reply to Forward event to another NetXMS server is not working on Thu, 29 Dec 2016 07:46:44 GMT]]>Hi Victor,

I am using netxms-2.0.7-x64.exe, last version of NetXMS server.
I am trying use reversed IP address of remote server 42.228.19.172 as you described in your post and its working excellent. It's working!!!!!!! Yeees!!!
I spend two day of analyzing this problem.
Victor, thank you a lot.
As anyone send this bug to the NetXMS develop team? If aren't I will send it.

with best regards,
Tomislav

]]>https://forum.netxms.org/post/21562https://forum.netxms.org/post/21562Thu, 29 Dec 2016 07:46:44 GMT<![CDATA[Reply to Forward event to another NetXMS server is not working on Wed, 28 Dec 2016 14:34:09 GMT]]>What version of NetXMS you are using? At some point there was a bug when IP address was inverted. Just in case, try to specify destination server address as 42.228.19.172.

Best regards,
Victor

]]>https://forum.netxms.org/post/21558https://forum.netxms.org/post/21558Wed, 28 Dec 2016 14:34:09 GMT<![CDATA[Reply to Forward event to another NetXMS server is not working on Wed, 28 Dec 2016 13:21:04 GMT]]>Thank you for your replay.

I have already check connection with paping aplication and ping and connection on port 4702 is established correctly.

Connecting to 172.19.228.42 on TCP 4702:

Connected to 172.19.228.42: time=1.00ms protocol=TCP port=4702
Connected to 172.19.228.42: time=1.00ms protocol=TCP port=4702
Connected to 172.19.228.42: time=1.00ms protocol=TCP port=4702
Connected to 172.19.228.42: time=1.00ms protocol=TCP port=4702

Connection statistics:
        Attempted = 4, Connected = 4, Failed = 0 (0.00%)
Approximate connection times:
        Minimum = 1.00ms, Maximum = 1.00ms, Average = 1.00ms

Is there some variable on source manager where is forward port defined?

with best regards,
Tomislav

]]>https://forum.netxms.org/post/21557https://forum.netxms.org/post/21557Wed, 28 Dec 2016 13:21:04 GMT<![CDATA[Reply to Forward event to another NetXMS server is not working on Wed, 28 Dec 2016 10:42:59 GMT]]>Hi,

make sure that destination server listen on port 4702 and that port is reachable from source server (not blocked by firewall, etc.). "Connect failed" indicates that source server was unable to establish TCP connection.

Best regards,
Victor

]]>https://forum.netxms.org/post/21556https://forum.netxms.org/post/21556Wed, 28 Dec 2016 10:42:59 GMT