Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM Documentation > Network Performance Monitor Getting Started Guide > Troubleshoot network issues > Monitor your network paths using SolarWinds NPM

Monitor your network paths using SolarWinds NPM

Created by Anthony.Rinaldi_ret, last modified by Chris.Moyer_ret on Oct 03, 2016

Views: 1,549 Votes: 1 Revisions: 2
Check out this video (5:10) on using NetPath™.

Use NetPath™ to discover and troubleshoot network paths hop-by-hop – not only the part of the network that you manage, but also nodes and links of your providers.


  • Creates a detailed (potentially multi-path) map between a Windows node and a destination you specify.
  • Overlays the path with performance metrics and device details of the nodes, interfaces, and connectors it finds.
  • Quickly identifies problem areas. Hover over objects to see more details using the Object Inspector, or drill down on managed nodes.



  • You must open certain ports on your firewall for network connectivity used by NetPath™. For more information, see the "NetPath™ Requirements" section in the SolarWinds Network Performance Monitor 12.0 Administrator Guide.
  • NTA 4.2 and NCM 7.4.1 are the minimum required versions to use the Orion integration features with NetPath™.

Create a NetPath™ service

In this scenario, Salesforce has been slow, and you want to analyze the path to find out where the problem is.

  1. Click My Dashboards > Network > NetPath Services.
  2. If this is your first time using NetPath™, you'll see an introductory wizard that shows how NetPath™ works. Otherwise, click Create New Service.
  3. In the Hostname field, enter, and in the Port field, enter 80.
  4. Enter Salesforce as the alias.
  5. Set the Probing Interval to 10 minutes, and click Next.

    Probing frequency determines how often Orion discovers the path and measures the path's performance.


  6. Assign a probe to the path.

    The Orion main poller includes a probe you can use, or you can add a probe to a Windows device.

  7. Click Create.

    It takes the system at least the time specified as the probing interval to map the path.

    For more information on NetPath™, or if you are unable to get NetPath™ working, see the "Discover your network paths" chapter in the SolarWinds Network Performance Monitor 12.0 Administrator Guide.


Troubleshoot with NetPath™

After NetPath™ maps the path, you can see your internal network, traversed segments of ISP networks, and the destination network, plus the details and statuses of the objects on the route.

You can use the controls in the top left of the page to zoom in and out, and to control the level of detail shown. The path between SolarWinds™ Austin HQ and Salesforce shows the maximum level of detail.


NetPath™ monitors paths at regular intervals (the probing interval) and keeps historical data, which is shown in the Path History section at the bottom of the page. You can see in this example that the path is fine now, but was red a few intervals ago.

Click the red bar to see the path at that time.


Notice that the path is different during this time period than the current time. That's normal. Paths can and do change over time.


If you look closely at the red object, you can see that it's actually two objects.


Double-click the object to expand it.


If you single-click the individual device that's causing the problem, the Object Inspector opens.


It looks like this device had high packet loss during this 10 minute time period, but the problem seems to be resolved. If you had caught this while it was happening, you could use the information in the Object Inspector to contact the device's owner and report the problem. And because NetPath™ keeps a history of each path, you can identify trends over time, and troubleshoot intermittent problems.

Last modified