• State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 788 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.

Help - Network Discovery not working against AWS

LatteLarry

Need some urgent help. Network Discovery does not find any subnets or nodes when scanning AWS subnets. The subnets exist with plenty of nodes on them. I suspect there is some sort of blocking or filtering on the AWS side that is preventing the discovery. Can anyone advise what the requirements are for Network Discovery to work? Ports, protocols, inbound\outbound, etc.

Parents
  • 0

    I've been testing this in different ways. What I have found is that discovery does not work at all, only discovery. I am trying to find primarily Windows and Linux nodes, but no subnets or nodes are found at all. Interestingly, I have both Windows and Linux nodes in AWS that are running the agent and monitored successfully. Even if I point the discovery directly at the IP of a monitored server, it finds nothing. Even if I have ICMP reply enabled in the discovery, nothing is found.

    For now, I have ensured TCP 17778, UDP 161, and ICMP are in the AWS networking security groups. I'm going to try to add TCP 135 and test today. If you can think of anything else, any help would be GREATLY appreciated!

Reply
  • 0

    I've been testing this in different ways. What I have found is that discovery does not work at all, only discovery. I am trying to find primarily Windows and Linux nodes, but no subnets or nodes are found at all. Interestingly, I have both Windows and Linux nodes in AWS that are running the agent and monitored successfully. Even if I point the discovery directly at the IP of a monitored server, it finds nothing. Even if I have ICMP reply enabled in the discovery, nothing is found.

    For now, I have ensured TCP 17778, UDP 161, and ICMP are in the AWS networking security groups. I'm going to try to add TCP 135 and test today. If you can think of anything else, any help would be GREATLY appreciated!

Children
No Data

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.