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

Additional Poller Agents

solaradmin

I am trying to utilize agents to communicate to my APE. But when I change polling engines from inside the Manage Agents settings. I get the below error. Hoping someone can provide me with a solution.

There was no response from the Agent Management Control Service located at "Name:17777".

I am running NPM 12 RC2

Find more posts tagged with

Accepted answers

All comments

nick_scott

Can you telnet on port 17777 from the device to the APE ?

solaradmin

Yes I am.

solaradmin

am*Can

daleharrisonips

Hi, I'm receiving this error currently with an additional poller I have on a different network/AD-Domain.

The Poller shows up as valid and connected, but every time I try to add a node to use this poller I get this error for some reason.

I see the successful connections through the firewalls on 17777 between the Orion server and the poller, but I just can't seem to use it for some reason.

Did you ever get this resolved?

Cheers,

Dale.

xpowels

Bump. Same issue. Two APEs, no working agents after upgrade.

jamshaw

I have same issue. I cannot add any additional pollers. I have validated that I can telnet to port 17777 as well. I also did a net stat and found that sure enough it is listening properly on the main orion site.

brave_beaver

Make sure whether Main poller's server can ping Additional poller's server using short host name (like 'WIN-SVR-2017' instead of 'WIN-SVR-2017.mydomain.com') and VICE VERSA.

In case the ping does not work, go to 'c:\Windows\System32\drivers\etc\hosts' file and add appropriate mapping line (on MP and AP is needed): <mp/ap_ip_address> <mp/ap_short_host_name>