Prerequisites

You must have administrator access on the Windows Server where OneIQ Pulse is installed.

Overview

The error message "The client cannot connect to the destination specified in the request" typically indicates that a client application or device is unable to establish a connection to the specified destination, such as a server, service, or resource.

Symptom

Hyper-V node collection fails with the following error message:

Connecting to remote server 10.0.2.200 failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic.

Troubleshooting

This issue typically arises when the Windows Remote Management (WinRM) service is not configured or allowed on the hosts. As a result, OneIQ Pulse is unable to establish a WinRM connection to the Hyper-V host.

To resolve this issue, you need to configure WinRM on the host. Here are the steps:

Run WinRM Quick Configuration: Open a command prompt with administrative privileges and run the command winrm quickconfig. This command will analyze and configure the WinRM service.
Enable PowerShell Remoting: Next, you need to enable PowerShell remoting which allows for the execution of PowerShell commands on remote computers. You can do this by running the command Enable-PSRemoting in the PowerShell console with administrative privileges.
Test WS-Management (WSMan) service: Finally, verify that the WS-Management (WSMan) service is running properly. You can do this by running the command Test-WSMan in the PowerShell console. This command checks the status of the WSMan service on local or remote computers.

Note that these commands should be executed on the Hyper-V host experiencing the issue. If you continue to experience problems after performing these steps, please consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM.