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

Orion 10 Unable to utilize network discovery to sites with NAT enabled

I have seen this has been a problem in the past and I am wondering if there is a fix for it.

I have 50 locations we are adding into monitoring that all have the same 192.168.254.X network. We established a VPN tunnel to each site and configured NAT on the remote end. When performing a discovery to the locations the page shows it is discovering names and connectivity (we can actually read the SNMP names as it goes through each one) but when it completes no nodes are found.

If I manually add a node it works without issue but the problem (other than the sheer volume of devices) is that I do not get the connectivity matrix to automatically build the topologies.

Is there any work around for this? I need a workable solution ASAP.

Find more posts tagged with

Accepted answers

All comments

tonyreel

Hi mdriskell,

I believe if you use the old discovery .exe that is in one of the solarwinds folders that it works. I have not done it myself but seen it discussed.

not sure what the name is. Ill have a look

tonyreel

I think sonar.exe will do the job. I have a feeling this might be part of the management toolset tho, so hopefully you have that.

mdriskell

The app didn't provide any better results. The app also doesn't do the connectivity information which is the main reason why we want to discover these nodes. I truly don't get why it fails...I watch it go through each device name in the network but when it finishes the only devices it discovers are the ones where SNMP failed.

jan1

Mike,

I suggest upgrading to 10.1.

This issue should be fixed there.

Thanks

Jan

mdriskell

Jan,

I have had a ticket open for about a week that is being worked by the developers. I'm pretty sure if this was fixed in 10.1 they would have informed me.

If someone can provide me definitive proof that this is fixed in 10.1 I will be happy to upgrade.

mdriskell

So Solarwinds support came back today and informed me that this is indeed fixed in 10.1. I upgraded this morning and the first discovery went off and all NAT devices have been properly discovered.

Apparently it was a known issue. The only thing I don't understand is why did this supposedly known issue have to go to dev to test and take a week to find out it was a known bug?

Alas we are running.