Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Netpath Probe on a Remote Network Not Working

Hi I've created a Netpath Probe on a remote Network and its not giving me any results. The Orion Server can't access the remote network, but it has full access to the Probe. The Probe can also fully communicate with the Server. I have setup a Netpath monitor on the Probe to monitor a destination in the remote network. The Probe has full access to the remote network. However, all that is reported is no data. Someone has said this is because the Orion Server can't see or communicate with anything on the remote network and so what I'm trying won't work. Is this correct? I thought only the Probe needed to communicate with everything on the remote network.

Can someone clarify this please?

Thanks,

Paul

Find more posts tagged with

Accepted answers

All comments

paul.kyte

Any takers on this challenging question. I'm sure someone can tell me the definitive answer.

Thanks,

Paul

superfly

You are correct that it is only the probe that needs to be able to communicate the remote network. It then sends this data back to Solarwinds.

https://documentation.solarwinds.com/en/success_center/npm/content/npm-create-a-probe.htm

Is there a firewall between Solarwinds and the probe? And are you 100% sure the probe can see the remote network? Do you have more details?

paul.kyte

Thank you Superfly,

There is a Firewall between Orion and the Probe but this contains a permit all IP between Orion and the Probe in both directions. So in essence theres nothing preventing either communicating with the other. I've also checked the routing tables on both sides of the Firewall and this is correct with routes to each other.

On the Orion admin page for Agents it shows the Probe as being online and active and if I look at the Plugins all are present including the Netpath plugin.

I was wondering if there is any sort of logfile on the Probe that can be viewed or if it can be put into debug mode and then one created?

Thank you for your help,

Paul

paul.kyte

Hi All,

I have managed to resolve the issue by looking at the Netpath Log on the Probe. I followed this article to give me debug information but there wasn't any:

NetPath graph issues: basic troubleshooting in NPM (solarwinds.com)

However it didn't show anything an didn't pull back any traces but on the debug view there was a tab for Logs and within this it gave locations of log files on the Probe. The one for the Netpath process was %ProgramData%\Solarwinds\Logs\Orion\NetPath.BusinessLayer.log

So I headed over to the Probe and took a look at the Netpath Log and it had a process that was constantly cycling with this error message within each cycle:

'SolarWinds.NetPath.Probe.Contract.Models.Settings' threw an exception. ---> SolarWinds.Newtonsoft.Json.JsonReaderException: Error parsing value. Path 'InterfaceIpAddress', line 2, position 25.

I did a bit of Googling on this and eventually got the following document:

https://support.solarwinds.com/SuccessCenter/s/article/NetPath-shows-the-error-No-Data-Found?language=en_US

This states that the Netpath Configuration file on the Probe has an incorrect value of *NULL* instead of *null*. The document told me the config file is in the following directory on the Probe:

c:\ProgramData\SolarWinds\Orion\NetPath\NetPathAgent.cfg

I duly amended this but still no joy so I compared this line to another probe that was working the value in this was just null without the asterisks. I tried this, rebooted, and brilliant, the Probe is working. So the cause was the 2nd line in the Netpath config file on the Probe and this is how it now looks and is working perfect:

"InterfaceIpAddress": null,

So thats it all working good. Thanks to Superfly who was trying to help me and from me its rotten tomatoes to all those engineers who said the Orion Server needs to see all the devices the Probe finds on the path to the destination. This is totally wrong. It makes you wonder what other things these engineers don't know or have got the completely wrong idea of.

superfly

Great to hear you've got it sorted! Nicely done