Windows Credentials Authentication failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2018 03:34 AM
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
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2018 06:30 AM
Hi everyone,
Ii have the same issue with my widows credentials for orchestration. (the non domain admin ones) Has this issue been solved?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2019 09:16 AM
did you ever get a resolution to this? We are a credentials error as well.
Connection Failed: java.lang.RuntimeException: com.snc.automation_common.integration.exceptions.InvalidOperationException: Not able to get the credential with the sysId: f1aaf6e04f21a600da710ad14210c7e3. If the credential is an external credential, please verify your external credential setup/configuration. Otherwise, please check if the credential is active.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2019 04:27 AM
Hi Thomas, i did solve the issue month ago. Reason was that we tried to access and execute on the domain controller directly from the mid server which is only possible if you use domain admin permissions. We accessed another server which then accessed the DC and it did work fine.