Меню

Эта ошибка обычно возвращается сервером http не поддерживающим протокол ws management

  • Remove From My Forums

  • Вопрос

  • Добрый вечер! Пробую настроить Direct Access в своей сети. Установил все службы. Запуская мастер начальной настройки и получаю следующую ошибку:

    Клиенту не удается подключиться к узлу назначения, указанному в запросе. Убедитесь, что служба на узле назначения
    работает и принимает запросы. Ознакомьтесь с журналами и документацией для определения запущенной на узле назначения службы WS-Managment (чаще всего это IIS или WinRM). Если это служба WinRM, то для анализа состояния и настройки этой
    службы используйте на удаленном узле команду «winrm quickconfig».

    Не могу понять куда это он не может подключиться. IIS локально запущен и работает.

Ответы

  • Выведите сервер в отдельную OU для исключения влияния групповых политик. Иначе долго будем траблшутить.

    • Предложено в качестве ответа

      29 ноября 2013 г. 8:20

    • Помечено в качестве ответа
      Petko KrushevMicrosoft contingent staff, Moderator
      29 ноября 2013 г. 8:20

Источник
  • Remove From My Forums

  • Question

  • New-PSSession : [myserver.com] Connecting to remote server myserver.com 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.
    At line:1 char:1
    + New-PSSession -ConnectionURI «$connectionUri» -ConfigurationName Micr …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException
        + FullyQualifiedErrorId : URLNotAvailable,PSSessionOpenFailed

    • Moved by

      Wednesday, December 4, 2019 6:22 PM
      Correct forum

Источник
  • Remove From My Forums

  • Question

  • New-PSSession : [myserver.com] Connecting to remote server myserver.com 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.
    At line:1 char:1
    + New-PSSession -ConnectionURI «$connectionUri» -ConfigurationName Micr …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException
        + FullyQualifiedErrorId : URLNotAvailable,PSSessionOpenFailed

    • Moved by

      Wednesday, December 4, 2019 6:22 PM
      Correct forum

Источник
title description author audience ms.topic ms.author manager localization_priority ms.custom search.appverid appliesto ms.date

Connecting to the remote server failed when start Management Shell or Console

Connecting to the remote server failed with the following error message when you start the Exchange Management Shell or the Exchange Management Console.

simonxjx

ITPro

troubleshooting

v-six

dcscontentpm

Normal

Exchange Server

CSSTroubleshoot

MET150

Exchange Server 2010 Service Pack 3

Exchange Server 2010 Enterprise

Exchange Server 2010 Standard

3/31/2022

«Connecting to the remote server failed with the following error message» error when you start the Exchange Management Shell or the Exchange Management Console

Symptoms

When you try to start the Microsoft Exchange Management Shell (EMS) or the Microsoft Exchange Management Console (EMC) on a server that is running Microsoft Exchange Server, you receive one of the following error messages:

  • Error message 1

    Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.

  • Error message 2

    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.

  • Error message 3

    Connecting to remote server failed with the following error message: The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. It was running the command ‘Discover-ExchangeServer -UseWIA $true -SuppressError $true’.

  • Error message 4

    Connecting to remote server failed with the following error message: The connection to the specified remote host was refused. Verify that the WS-Management service is running on the remote host and configured to listen for requests on the correct port and HTTP URL. For more information, see the about_Remote_Troubleshooting Help topic.

  • Error message 5

    Connecting to remote server failed with the following error message: The WinRM client received an HTTP status code of 403 from the remote WS-Management service.

  • Error message 6

    Connecting to the 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.

  • Error message 7

    Connecting to remote server 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:

  • Error message 8

    Connecting to remote server failed with the following error message: The WS-Management service does not support the request.

  • Error message 9

    Connecting to remote server failed with the following error message: The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer.

Resolution

To resolve these problems, run the «Exchange Management Troubleshooter» (EMTshooter).

About the EMT shooter

The EMTshooter runs on the local (target) Exchange server and tries to identify potential problems that affect the management tools that are connected to it.

The troubleshooter runs in two stages. First, it examines the IIS Default Web Site, the PowerShell vdir, and other critical areas to identify known causes of connection problems. If the tool identifies a problem that affects one of the pre-check processes, it makes a recommendation to resolve the problem. If the pre-checks pass, the troubleshooter tries to connect to the server exactly like the management tools would connect. If that connection attempt still causes a WinRM-style error, the troubleshooter tries compare that error to a list of stored strings that are collected from related support cases. If a match is found, the troubleshooter displays the known causes of that error in the CMD window.

The following screen shot shows how this display might appear.

:::image type=»content» source=»media/connecting-remote-server-failed/emt-shooter.png» alt-text=»Screenshot of how this display might appear.»:::

The EMTshooter logs events in the «Microsoft-Exchange-Troubleshooters/Operational» event log. All results that are displayed in the CMD window are also logged in the event log to create a record.

Things to remember

  • Depending on your current settings, you may have to adjust the execution policy on your computer to run the troubleshooter by using one of the following commands:

    • Set-ExecutionPolicy RemoteSigned

    • Set-ExecutionPolicy Unrestricted

      [!IMPORTANT]
      Remember to revert to the usual settings after you run the troubleshooter.

  • You must run this version of the troubleshooter on the server that is running Exchange Server that the management tools do not connect to.

  • In order to run the troubleshooter, you must have the user rights to log on locally to the Exchange server. This is a current requirement of the tool. Additionally, you must have the user rights to run Windows PowerShell.

How to install EMTshooter

To install the EMT shooter, follow these steps:

  1. Download the troubleshooter compressed file that has a .zip filename extension from here.
  2. Extract the four files that are included in the .zip file into a folder, and then rename the file extensions to .ps1.
  3. Run EMTshooter.ps1 from a standard (and local) Windows PowerShell window.

References

For more information about the problems that are processed by EMTshooter and the causes of some of those problems, see the following Exchange Team Blog articles:

Troubleshooting Exchange 2010 Management Tools startup issues

Resolving WinRM errors and Exchange 2010 Management tools startup failures

Источник
title description author audience ms.topic ms.author manager localization_priority ms.custom search.appverid appliesto ms.date

Connecting to the remote server failed when start Management Shell or Console

Connecting to the remote server failed with the following error message when you start the Exchange Management Shell or the Exchange Management Console.

simonxjx

ITPro

troubleshooting

v-six

dcscontentpm

Normal

Exchange Server

CSSTroubleshoot

MET150

Exchange Server 2010 Service Pack 3

Exchange Server 2010 Enterprise

Exchange Server 2010 Standard

3/31/2022

«Connecting to the remote server failed with the following error message» error when you start the Exchange Management Shell or the Exchange Management Console

Symptoms

When you try to start the Microsoft Exchange Management Shell (EMS) or the Microsoft Exchange Management Console (EMC) on a server that is running Microsoft Exchange Server, you receive one of the following error messages:

  • Error message 1

    Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.

  • Error message 2

    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.

  • Error message 3

    Connecting to remote server failed with the following error message: The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. It was running the command ‘Discover-ExchangeServer -UseWIA $true -SuppressError $true’.

  • Error message 4

    Connecting to remote server failed with the following error message: The connection to the specified remote host was refused. Verify that the WS-Management service is running on the remote host and configured to listen for requests on the correct port and HTTP URL. For more information, see the about_Remote_Troubleshooting Help topic.

  • Error message 5

    Connecting to remote server failed with the following error message: The WinRM client received an HTTP status code of 403 from the remote WS-Management service.

  • Error message 6

    Connecting to the 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.

  • Error message 7

    Connecting to remote server 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:

  • Error message 8

    Connecting to remote server failed with the following error message: The WS-Management service does not support the request.

  • Error message 9

    Connecting to remote server failed with the following error message: The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer.

Resolution

To resolve these problems, run the «Exchange Management Troubleshooter» (EMTshooter).

About the EMT shooter

The EMTshooter runs on the local (target) Exchange server and tries to identify potential problems that affect the management tools that are connected to it.

The troubleshooter runs in two stages. First, it examines the IIS Default Web Site, the PowerShell vdir, and other critical areas to identify known causes of connection problems. If the tool identifies a problem that affects one of the pre-check processes, it makes a recommendation to resolve the problem. If the pre-checks pass, the troubleshooter tries to connect to the server exactly like the management tools would connect. If that connection attempt still causes a WinRM-style error, the troubleshooter tries compare that error to a list of stored strings that are collected from related support cases. If a match is found, the troubleshooter displays the known causes of that error in the CMD window.

The following screen shot shows how this display might appear.

:::image type=»content» source=»media/connecting-remote-server-failed/emt-shooter.png» alt-text=»Screenshot of how this display might appear.»:::

The EMTshooter logs events in the «Microsoft-Exchange-Troubleshooters/Operational» event log. All results that are displayed in the CMD window are also logged in the event log to create a record.

Things to remember

  • Depending on your current settings, you may have to adjust the execution policy on your computer to run the troubleshooter by using one of the following commands:

    • Set-ExecutionPolicy RemoteSigned

    • Set-ExecutionPolicy Unrestricted

      [!IMPORTANT]
      Remember to revert to the usual settings after you run the troubleshooter.

  • You must run this version of the troubleshooter on the server that is running Exchange Server that the management tools do not connect to.

  • In order to run the troubleshooter, you must have the user rights to log on locally to the Exchange server. This is a current requirement of the tool. Additionally, you must have the user rights to run Windows PowerShell.

How to install EMTshooter

To install the EMT shooter, follow these steps:

  1. Download the troubleshooter compressed file that has a .zip filename extension from here.
  2. Extract the four files that are included in the .zip file into a folder, and then rename the file extensions to .ps1.
  3. Run EMTshooter.ps1 from a standard (and local) Windows PowerShell window.

References

For more information about the problems that are processed by EMTshooter and the causes of some of those problems, see the following Exchange Team Blog articles:

Troubleshooting Exchange 2010 Management Tools startup issues

Resolving WinRM errors and Exchange 2010 Management tools startup failures

Источник

I’ve had two annoying PowerShell errors today, both for the same server:

Enter-PSSession : Connecting to remote server server-a.rcmtech.co.uk 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.

The standard “internet” response to this is to open an Administrator command prompt and run

winrm qc

(or winrm quickconfig). Or open an Administrator PowerShell prompt and run:

Enable-PSRemoting

But these are quite annoying solutions if you know that it should be working, and indeed is working on all your other servers, because you’ve configured it via Group Policy! There’s no harm in running the commands anyway, but most likely they’ll just come back and say “already configured” or words to that effect.

So the fix (for me) for the above error was to check what IP addresses the listener was listening on using:

netstat -aon | find "5985"

where 5985 is the default port used by WinRM. You should see the system process (ID 4) listening on 0.0.0.0 like this:

TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING 4

However on my problem server it was listening on 127.0.0.1. This can be confirmed using:

netsh http show iplisten

and you’ll only see 127.0.0.1 in the list.
On the problem server itself you’ll find that using:

Enter-PSSession -Computername localhost

works, whereas:

Enter-PSSession -Computername server-a.rcmtech.co.uk

does not.
localhost is the name for the loopback address 127.0.0.1 whereas the fully qualified server name will give you the IP address of the server as seen from your network.
The fix for this is to delete the loopback address from the http listener, which then makes it listen on all valid addresses:

netsh http delete iplisten 127.0.0.1.

Check what addresses it is now listening on (plus the port) by using:

winrm e winrm/config/listener

Problem solved. Or not, I then got this error:

Enter-PSSession : Connecting to remote server server-a.rcmtech.co.uk 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.

Which it turns out can be caused by having IPv6 enabled on the server.
In the netstat output (see above) I also had some IPv6 addresses showing as listening on port 5985.
I don’t use IPv6 but it’s on by default in Windows and will auto-assign itself a link local address (starts with fe80:). So I disabled IPv6 and the error went away. There’s also a workaround using the hosts file if you don’t want to disable IPv6.

Update

This might also be caused because you have the following group policy configured:

Computer ConfigurationPoliciesAdministrative TemplatesWindows ComponentsWindows Remote ManagementWinRM ServiceAllow remote server management through WinRM

And in the settings for that policy, you only have a * in the box for IPv4, and nothing in the box for IPv6. Add a * in the IPv6 box too.

Источник

PS установлен, настроен прослушивать по HTTP и HTTPS. Но при попытке

enter-pssession -connectionuri http://127.0.0.1 -sessionOption (new-pssessionoption -SkipCACheck -SkipCNCheck -SkipRevocationCheck)

выдается ошибка Enter-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 HT
TP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting
Help topic.
At line:1 char:16
+ enter-pssession <<<<  -connectionuri http://127.0.0.1 -sessionOption (new-pssessionoption -SkipCACheck -SkipCNCheck —
SkipRevocationCheck)
    + CategoryInfo          : InvalidArgument: (http://127.0.0.1/:Uri) [Enter-PSSession], PSRemotingTransportException
    + FullyQualifiedErrorId : CreateRemoteRunspaceFailed

не говоря уже и с удаленного хоста

по HTTPS тоже не работает:

Enter-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.

на других серверах работает

x86, server 2003r2

заранее спасибо за ответы

Источник

0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии

А вот еще интересные материалы:

  • Яшка сломя голову остановился исправьте ошибки
  • Ятрогенная патология врачебные ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного где ошибка
  • Эти документы необходимо отксерить ошибка

    • ➤