nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Error adding host

NasaGeek

I get this error when adding a host to the priomary polling engine and click "validate host". But when I chose our other engine, I do not get the error.

"Test Failed. There was no endpoint listening at net.tcp://our-solarwinds-box:17777/orion/npm/businesslayer that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details."

Find more posts tagged with

Accepted answers

morgolis

Check the 'our-solarwinds-box' server has a service listen on the IP of the engine for port 17777.

Open a command line and type this in:

netstat -na | find /i "17777"

Make sure that either it shows the IP address bound on the NIC or it binds the service to all listening IP's. It should look like this: 0.0.0.0:17777 or xxx.xxx.xxx.xxx.:17777

If the service is running, next I would start checking to see if the windows firewall is active and stopping the in bound connection. Turn off the windows firewall and try it again, if it works then you know that was the problem.

All comments

morgolis

Check the 'our-solarwinds-box' server has a service listen on the IP of the engine for port 17777.

Open a command line and type this in:

netstat -na | find /i "17777"

Make sure that either it shows the IP address bound on the NIC or it binds the service to all listening IP's. It should look like this: 0.0.0.0:17777 or xxx.xxx.xxx.xxx.:17777

NasaGeek

The firewall is not running.

netstat -na | find /i "17777"

TCP    0.0.0.0:17777          0.0.0.0:0              LISTENING
TCP    127.0.0.1:1789         127.0.0.1:17777        ESTABLISHED
TCP    127.0.0.1:17777        127.0.0.1:1789         ESTABLISHED
TCP    our-solarwinds-box:1788    our-secondary-poller:17777   ESTABLISHED
TCP    our-solarwinds-box:2547    our-secondary-poller:17777   ESTABLISHED
TCP    our-solarwinds-box:2591    our-secondary-poller:17777   ESTABLISHED

Perhaps I will have to open a ticket.

morgolis

Last thing I can think of is that the DNS isn't working properly when it tries to resolve the hostname of 'our-solarwinds-box'.

Try to ping the DNS name 'our-solarwinds-box' from both machines, if one fails then you know the issue. You may need to add an entry to the windows hosts file in located C:\Windows\System32\drivers\etc with the proper resolution IP address.

NasaGeek

Not DNS either. This just happened recently and we have not made any changes to the system. I am opening a ticket. I will post the result from that when this is resolved.