Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Orion Platform > Orion Documentation > Additional polling engine/HA server cannot connect to the main polling engine

Additional polling engine/HA server cannot connect to the main polling engine

Created by Sean.Nyhan, last modified by Magdalena.Markova on Jun 13, 2018

Views: 70 Votes: 0 Revisions: 6

Updated: April 4, 2018


When you install an additional polling engine and cannot connect it to the main polling engine in a different domain, use FQDN to enable hostname resolution.


  • Orion Platform products installed with a scalability engine (additional polling engine, additional web server or high availability)


The main polling engine and the additional polling engine are located on different domains so hostname resolution is not working. 


Make sure that all required ports are open and that you have excluded required ports and folders from antivirus protection.

Use the fully qualified domain name (FQDN).

  1. Check and confirm both polling engines are in the same time zone and that the times are synchronized.
  2. Add an entry to the hosts files on the primary polling engine and on the additional polling engine so that they are able to communicate via the hostname.
  3. Add a manual record in the DNS at a later stage.




Suggested Tags:  APE, Additional poller to main poller connectivity issue, DNS, FQDN


A reason for rework or Feedback from Technical Content Review:



Last modified