• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 374 views
  • Users 0 members are here
Options
Related
This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Cannot add a Windows node on additional polling engine

seniorza

Hi Everyone,

My team's managed to get an additional polling engined installed for our SAM installation. Our central Orion server is hosted on the internet and we've installed an additional polling engine on a private network successfully after allowing inbound traffic over the internet to the Orion server for TCP 17777 and for MSSQL. The additional polling engine is successfully registered on the Orion server.

When adding a Windows node to use the new polling engine we are now met with a DNS error indicating that the polling engine cannot be resolved.

Any ideas please?

Thanks,

Andrew‌ and martinoosthuyzen‌

pastedImage_0.jpg

  • 0

    I would start by RDPing to the primary Orion server and doing an NSLOOKUP or ping of the additional polling engine (APE). If you can't resolve the name of the APE from the primary server, then you do, in fact, have a DNS issue that you need to resolve.

  • 0

    Thanks clubjuggle. I assumed that the APE would work with only TCP traffic open from the APE to the Orion server rather than bi-directional. This makes my scenario more complicated - looks like I'm going to need to investigate use of a VPN.

  • 0 in reply to seniorza

    The main Orion server needs to be able to talk to the APE as well in order to allow management of the APE itself. In addition, best practice is that the APE shouldn't monitor itself (I monitor all my APEs from the primary server).

    If you're setting up Windows machines behind a firewall, you could consider using agents on those machines. If you configure the agents for agent-initiated communication, you only need TCP open one way on one port, in the direction from the monitored system(s) to the Orion poller.

    If you prefer to use a poller at the firewalled site, you could also NAT the address of the APE (coupled with an ACL to restrict the traffic appropriately) as an alternative to a VPN.

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.

SolarWinds Customer Success Center Certification Media Vault Link Accounts
About THWACK Blogs For Government Edit Settings Free Tools & Trials
Legal Documents Terms of Use Privacy California Privacy Rights Security Information
©2024 SolarWinds Worldwide, LLC. All Rights Reserved.