It works as following. First of all, you have to enable TCP proxy on a proxy agent. By default it will be agent running on NetXMS server, or if zoning is enabled, agent running on zone proxy. When you run object tool with TCP proxy option, client will open random local port for listening, then establish tunnel to proxy agent, and when you open TCP connection to this random local port, proxy agent will establish TCP connection to target node on port set in object tool configuration.
So, for example, let's say you have Synology device reachable at 192.168.1.10 by the server. You will do the following steps:
1. You Synology device to NetXMS as a node, and specify 192.168.1.10 as primary IP address.
2. Enable TCP proxy on server's agent.
3. Enable TCP port forwarding option in object tool, and use URL http://${local-address}:${local-port}
When running on Synology node, this tool should open browser on local host which will be forwarded to Synology device.
Best regards,
Victor
So, for example, let's say you have Synology device reachable at 192.168.1.10 by the server. You will do the following steps:
1. You Synology device to NetXMS as a node, and specify 192.168.1.10 as primary IP address.
2. Enable TCP proxy on server's agent.
3. Enable TCP port forwarding option in object tool, and use URL http://${local-address}:${local-port}
When running on Synology node, this tool should open browser on local host which will be forwarded to Synology device.
Best regards,
Victor