Windows Discovery fails even when credential is Valid

[haruesgap]

Hi All, 

I'm looking for some wisdom or other ideas I've been not thinking of. 

I have a Windows service account with local admin rights as well for interactive logon active and I don't have issues while login directly to the host I want to discover. However from mid server I'm seeing this error:

Target is blacklisted. No valid credential found for type [Windows]

Although I've added an affinity entry and I'm seeing through Firewall traffic over port 135 it seems like discovery is not working properly. I've also noted that on the remote host I'm not seeing any login failure for the service account I'm using. and got this from powershell on the MID Server:

PS C:\Users\us-svcsnxxxxxx> gwmi win32_operatingsystem -computer 1x.xx.xx.xx -credential 'us\us-svcsnxxxxxxx'
gwmi : The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
At line:1 char:1
+ gwmi win32_operatingsystem -computer 10.43.20.3 -credential 'us\us-sv ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Get-WmiObject], COMException
+ FullyQualifiedErrorId : GetWMICOMException,Microsoft.PowerShell.Commands.GetWmiObjectCommand

RPC is enabled and working without issues. I'm running out of ideas. Anyone has faced this issue before?

[Safted82]

If Windows Discovery fails with valid credentials, verify the service account has local administrator rights and WMI permissions on the target server, ensure network connectivity on required ports (135, 49152-65535) for RPC, check for WMI and RPC service availability on the target, confirm the account isn't locked out, and ensure correct WMI timeout settings. You can test connectivity using PowerShell and Test-NetConnection, and use the WBEMTEST utility to verify WMI functionality independently of the discovery tool.