<![CDATA[Unable to add a second node (same IP)]]>Hello,

I am currently trying to monitor both a Terminal Server and Domain Controller. I have the Terminal Server added as a node using the hostname remote.exmaple.com which uses port 4701 (translates to 4700). I've then also tried to add the Domain Controller which sits on the same network using the hostname and IP which uses port 4702 and translates to 4700 but I get the error;

'Create new node' has encountered a problem.

Cannot create node object "DC1": IP conflict with node TS1

Any ideas on how I can resolve this or get around it?

]]>https://forum.netxms.org/topic/5602/unable-to-add-a-second-node-same-ipRSS for NodeFri, 13 Nov 2026 15:21:22 GMTWed, 06 Jun 2018 10:34:59 GMT60<![CDATA[Reply to Unable to add a second node (same IP) on Thu, 07 Jun 2018 13:38:50 GMT]]>Hi,

NetXMS requires unique IPs per zone. As you are using the same IP twice (the public IP), you are seeing that error.

You probably want to either:

  1. use a proxy node in the network (e.g. only your DC or RDS) and configure other hosts in the network to talk to the proxy/allow the proxy to talk to them. If you search the forum you should be able to find some help on how to set this up. Documentation can be found here
  2. use Agent Tunnels to have each node talk back to the server instead. This is a bit more involved to set up, but means you are not depending on a single proxy node for all agents behind some NAT device. Documentation can be found here. There is also an older forum post here back from when I first struggled with setting this up.  ;D

Some not so great (read: "terrible, don't do this") options for the sake of completeness:

  • If you have plenty of public IPs, you can create each port forward with a separate public IP
  • You can create a separate zone for each server. IPs only have to be unique across zones.

Cheers

]]>https://forum.netxms.org/post/24387https://forum.netxms.org/post/24387Thu, 07 Jun 2018 13:38:50 GMT