Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Nodes with the same host name but different IP addresses are not added after discovery

Nodes with the same host name but different IP addresses are not added after discovery

Created by Beatrix.Turan, last modified by MindTouch on Jun 23, 2016

Views: 1,113 Votes: 1 Revisions: 3


When Network Sonar Discovery discovers nodes with the same host name but different IP addresses, only the first node is added.


All NPM versions


By design, Network Sonar Discovery only adds a single node in case of duplicates.


Perform any of the following actions:

  • Add the nodes manually one by one. 
  • Disable node de-duplication.
    ​Warning: SolarWinds strongly recommends that you only edit configuration files as instructed. Any additional modifications to the configuration file may result in system performance issues or may create an error state.
    1. Go to %Program Files%\SolarWinds\Orion
    2. Open the SolarWinds.Orion.Discovery.Job.dll.config file in a text editor.
    3. In the following lines, change the value from "false" to "true":
      <add key="DisableSysNameDuplicateDetector" value="false"/>
      <add key=“DisableDNSDuplicateDetector" value="false"/>
    4. Save the file.
    5. Restart all services in the Orion Service Manager.


Last modified