Discovery Credentials

carloschaluisan
Kilo Contributor

While running our Discovery Schedules, a significant amount of authentication / credential issues are being generated. The errors with the highest occurrence are:

  • Connection failed to WMI service. Error: Permission denied
  • SSHCommand: No valid credential found for types [SSH Password,SSH Private Key]
  • Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Here is what we've done so far:

  • Confirmed the usernames and passwords in the Credentials table are correct Confirmed the MID Servers are up.
  • Firewalls in the Host Machines where the MID servers are installed are disabled
  • Set mid.use_powershell = true in each MID Server
  • Set mid.powershell.use_credentials = true in each MID server
  • Set mid.powershell.local_mid_service_credential_fallback = false in each MID server
  • Manually ran WMI (gwmi) queries and tested SSH from the Host servers where the MID servers are installed and confirmed access is granted and data is returned.

Any troubleshooting suggestions would be greatly appreciated...

20 REPLIES 20

carloschaluisan
Kilo Contributor

Thanks to each of you for your help. For the WMI issue, we found the cause of the problem to be a Group Policy change I was unaware of.   Our AD team will have to push an update.   Using a couple of test target devices we noticed the usernames included in the credential table were no longer in the devices.


You're welcome, AD GPO is wonderful automation till it isn't


sai3072
Mega Contributor

I'm also facing the same problem when iam entering windows machine credentials its showing "authentication failed", i also checked with another machine credentials even that time also showing authentication failed.why??? where will the be problem??


Make sure the format is domain\user account. More details would help too


sai3072
Mega Contributor

my network is in workgroup not in domain..