Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Unable to add a second node (same IP)

Unable to add a second node (same IP)

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 14.8k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T
    T
    TICK_TEL
    wrote on last edited by
    #1

    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?

    1 Reply Last reply
    0
    • T
      T
      Tursiops
      wrote on last edited by
      #2

      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

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      Powered by NodeBB Contributors
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups