Search Engine: Elastic

Article ID: 133178, created on Sep 14, 2018, last review on Sep 14, 2018

  • Applies to:
  • Operations Automation


Various Exchange-related tasks may fail.

The Exchange Management Console cannot connect to the local server. It shows the error like below:

VERBOSE: Connecting to
New-PSSession : [] Connecting to remote server failed
with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the
requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the
WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic.

However, it is possible to connect to the same server from another computer:

[PS] C:\Windows\system32>Enter-PSSession -ComputerName
[]: PS C:\Users\pem_admin\Documents> hostname


The server has 2 IP addresses:

  • - bound to Default Web Site in IIS
  • - bound to AutodiscoverRedirectSite in IIS

On resolving local hostname Windows takes an IP address with a higher value, regardless to actual DNS settings. As a result, the hostname is resolved to the IP, which is not bound to Default Web Site. As a result, PowerShell cannot establish a connection.


It is recommended to use an IP address with a higher value for the website Default Web Site on Exchange mailbox servers.

5356b422f65bdad1c3e9edca5d74a1ae 8fc71f07abe5b233fea1ae0377cd5e3d

Email subscription for changes to this article
Save as PDF