Applications Systems

The WinRM client cannot process the request. Default authentication may be used with an IP address under the following conditions: the transport is HTTPS or the destination is in the TrustedHosts list, and explicit credentials are provided.

This article discusses about an error message generated when configuring AppInsight for IIS on nodes: "Connecting to remote server failed with the following error message : The WinRM client cannot process the request. Default authentication may be used with an IP address under the following conditions: the transport is HTTPS or the destination is in the TrustedHosts list, and explicit credentials are provided. Use winrm.cmd to configure TrustedHosts."

First published date

10/2/2019 7:51 AM

Last published date

9/14/2023 1:09 AM

Overview

When configuring AppInsight for IIS on target servers, or Appinsight for Active Directory the following error message is displayed:

"Connecting to remote server failed with the following error message : The WinRM client cannot process the request. Default authentication may be used with an IP address under the following conditions: the transport is HTTPS or the destination is in the TrustedHosts list, and explicit credentials are provided. Use winrm.cmd to configure TrustedHosts."

Product section

Server Application Monitor

Cause

  • SAM server is not included in the TrustedHosts List of the target node.
  • TrustedHosts is set DNS instead of the IP Address
  • PSRemoting is not enabled on Orion Server and the Target Server

Resolution

Configure WinRM on SAM server

NOTE: Make sure that PSRemoting is enabled on the Orion server and the Target server
  1. Run Command Prompt on SAM Server as Administrator
  2. Enter the following PowerShell command
# Scripts are not supported under any SolarWinds support program or service.
# Scripts are provided AS IS without warranty of any kind. SolarWinds further
# disclaims all warranties including, without limitation, any implied warranties
# of merchantability or of fitness for a particular purpose. The risk arising
# out of the use or performance of the scripts and documentation stays with you.
# In no event shall SolarWinds or anyone else involved in the creation,
# production, or delivery of the scripts be liable for any damages whatsoever
# (including, without limitation, damages for loss of business profits, business
# interruption, loss of business information, or other pecuniary loss) arising
# out of the use of or inability to use the scripts or documentation.

Enable-PSRemoting -Force

Then configure the trusted hosts by running the following commands from Command Line:
  
rem Scripts are not supported under any SolarWinds support program or service.
rem Scripts are provided AS IS without warranty of any kind. SolarWinds further
rem disclaims all warranties including, without limitation, any implied warranties
rem of merchantability or of fitness for a particular purpose. The risk arising
rem out of the use or performance of the scripts and documentation stays with you.
rem In no event shall SolarWinds or anyone else involved in the creation,
rem production, or delivery of the scripts be liable for any damages whatsoever
rem (including, without limitation, damages for loss of business profits, business
rem interruption, loss of business information, or other pecuniary loss) arising
rem out of the use of or inability to use the scripts or documentation.

winrm quickconfig
winrm set winrm/config/client '@{TrustedHosts="0.0.0.0"}'


NOTE:

1. You can replace * with the IP address of the SAM server.
2. Setting up the trusted host should always point at the IP address not the DNS name of the server.