AWS discovery is not discovering any VM's
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2020 08:10 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2020 11:24 PM
okay. You are right. ServiceNow does not give details of the rights on the target machine you want to scan, but it is a generally accepted rule that you need to have admin privileges, so please start with that.
Please try to run quick discovery first by giving the IP of the server or VM you are trying to scan to ensure that there are no problems before running the discovery at data center level.
Please like or accept solution so that it helps others too
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2020 11:45 PM
Another reason I think you should try quick discovery is the following:
There is a known error when Shazam tries very large IP ranges which in your case might be a data center, so my suggestions try:
- quick discovery first
- short IP range which should be the VLAN to which this particular VM belongs
Please refer to this:
https://hi.service-now.com/kb_view.do?sysparm_article=KB0693814