<![CDATA[Agent Tunnel Port Configuration]]>Is there a way to change the Agent Tunnel Port from 4703 to port 80 or 443 for example? If not, I'd like to make a feature request to allow this. Use case, some of my clients have strict firewall rules and do not allow traffic out except on specific ports, with typical web ports (80/443) being allowed.

Thank you,
Gary

]]>https://forum.netxms.org/topic/5411/agent-tunnel-port-configurationRSS for NodeFri, 13 Nov 2026 18:38:42 GMTThu, 25 Jan 2018 14:46:58 GMT60<![CDATA[Reply to Agent Tunnel Port Configuration on Wed, 28 Feb 2018 16:10:17 GMT]]>Hi,

you can also add any missing configuration parameter directly from UI (there is option "add parameter" in server configuration view) or using nxdbmgr:

nxdbmgr set AgentTunnelListenPort 443

Best regards,
Victor

]]>https://forum.netxms.org/post/23953https://forum.netxms.org/post/23953Wed, 28 Feb 2018 16:10:17 GMT<![CDATA[Reply to Agent Tunnel Port Configuration on Wed, 28 Feb 2018 15:39:01 GMT]]>I have tested this with agent 2.2.4 and was able to use ServerConnection = <server_ip>:<port> in the agent config.

Server side I needed to add the parameter (see below) to the config table using my database manager

AgentTunnelListenPort	443	1	1	I	N	Port server listens on for Agent Tunnels	NULL	4703
]]>https://forum.netxms.org/post/23951https://forum.netxms.org/post/23951Wed, 28 Feb 2018 15:39:01 GMT<![CDATA[Reply to Agent Tunnel Port Configuration on Tue, 06 Feb 2018 14:10:09 GMT]]>Maybe this is part of the bug. I am on version 2.2.3 and do not have the AgentTunnelListenPort parameter in my server configuration (or I am looking in the wrong place).

Looking forward to the next release as I am eager to get the rest of my clients on NetXMS.

tunnel_params.PNG

]]>https://forum.netxms.org/post/23828https://forum.netxms.org/post/23828Tue, 06 Feb 2018 14:10:09 GMT<![CDATA[Reply to Agent Tunnel Port Configuration on Tue, 06 Feb 2018 09:17:47 GMT]]>Hi,

it is supposed to be. You can set listening port on server by changing parameter AgentTunnelListenPort, and on agent side you can specify port after : in ServerConnection parameter. However, due to a bug, agent will always connect to port 4703. It is fixed in current development branch and fix will be included into next release.

Best regards,
Victor

]]>https://forum.netxms.org/post/23821https://forum.netxms.org/post/23821Tue, 06 Feb 2018 09:17:47 GMT