Windows Credentials Authentication failed

[Gaetano De Mitr]

Hi,

I'm configuring my Windows Credentials to discovery but give me an error "Authentication failed".

This is my ECC queue record:

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<results error="CommandPipeline: Adding target to blacklist. No valid credential found for type [Windows]" probe_time="3203" result_code="42">
<result error="CommandPipeline: Adding target to blacklist. No valid credential found for type [Windows]" name="">
<debug_info>
{"debug_info":[{"192.168.1.196":{"credentials_attempted":[{"credential_type":"Windows","credential_success":false}],"adding_key_to_target_blacklist":true,"connection_parameters":{"credential_types":["Windows"],"target":"192.168.1.196"}}}]}
</debug_info>
</result>
<parameters>
<parameter name="agent" value="mid.server.midserver_prod1"/>
<parameter name="response_to" value=""/>
<parameter name="from_sys_id" value=""/>
<parameter name="source" value="192.168.1.196"/>
<parameter name="priority" value="0"/>
<parameter name="agent_correlator" value=""/>
<parameter name="skip_sensor" value="true"/>
<parameter name="processed" value=""/>
<parameter name="error_string" value=""/>
<parameter name="sys_id" value="d7a01532db09df4005235cd4dc9619fc"/>
<parameter name="sequence" value="1626c225cfe0000001"/>
<parameter name="from_host" value=""/>
<parameter name="sys_created_on" value="2018-03-28 10:23:34"/>
<parameter name="name" value=""/>
<parameter name="topic" value="CommandPipeline"/>
<parameter name="state" value="ready"/>
<parameter name="queue" value="output"/>
<parameter name="ecc_queue" value="d7a01532db09df4005235cd4dc9619fc"/>
</parameters>
</results>

I'm using my Administrator credentials host, but not working.

Moreover powershell 2.0> is enabled and 135 port listening.

What is the problem?

Edit (Discovery Log):

Information Active, couldn't classify: No WMI connection, now finished WMIRunner Windows Classify 192.168.1.196
Warning User credentials cannot be used for local connections WMIRunner Windows Classify 192.168.1.196
Warning Failure(s) with available Windows credentials from the instance. WMIRunner Windows Classify 192.168.1.196

[James Hammond]

Hi Gaetano,

Have you checked that Windows Firewall has both Inbound & Outbound access on port 135, in case there is a rogue firewall setting; and I would also suggest that you verify the Credential record you created has the ''Applies to" field set to "All MID servers"; then restart your MID Server and try the same operation again.

[Gaetano De Mitr]

the firewall is disabled.

[James Hammond]

Did you check the second option as well?

verify the Credential record you created has the ''Applies to" field set to "All MID servers"; then restart your MID Server

[blazye44]

Gaetano, 

First i would check to see if you can use the credential on the server. Discovery> Credential and seleet test credentials. Then make sure that the Mid server being used is cofigured to use the credentials and check James's suggestions. 

Eddie