Discovery is failing with Credential issue

[UdayReddy]

Recently, we have moved the servers from on-premesis to Cloud. When we are trying to discover them using the account based and IAM-role based. We discovered the Virtual machines successfully. when we are trying to discover the account-based, we are getting the attached errors, eventhough we have added the credentials. Can someone please guide us, what else we have to troubleshoot?

[Hanna_G]

Hey @UdayReddy 

This error is telling you that you need to enable nmap on your Mid server(s), whichever servers you are using to do discovery you need to do these steps: Install and uninstall Nmap on a MID Server • Australia ServiceNow AI Platform Capabilities • Docs | ...
This looks like the host you are discovering doesn't have the correct credentials available. Could it be that you don't have the correct permissions with the account? You need admin permissions, so if its a windows machine for example, this would need a windows account with admin credentials. 

[UdayReddy]

Hi Hanna,

We have added the 'Service Account' in the 'Administrators group' for the given target host. Still, they are not working. Are we missing something apart from that?

[Hanna_G]

Hello,
It could be a number of things, I'd get the logs from the ECC Queue/Mid Server and see what is happening. 
It could be that WinRM isn't enabled on the host, that your service account isn't domain joined or firewall issues. 
@Selva Arun has done a fantastic reply here to similar issues: Windows Discovery fails even when credential is Va... - ServiceNow Community
ServiceNow have also provided documentation on Credential Troubleshooting. Credentials troubleshooting • Australia Platform security • Docs | ServiceNow
I think your next important step is to look at the logs & payloads to see where the error is happening and then troubleshoot from there.