WINRM Issue - WinRM service could not receive WS-Management requests

Hello,

I come across a scenario, where WinRM service could not receive WS-Management requests and event viewer is filling up with Error Event 10150 and Source: WinRM.

Hmmmm, what do we do now ???

  • I manually created a listener for WinRM service on different server, by using following command.
winrm quickconfig

  • After which  i tried checking the listener on it, by using below command

winrm enum winrm/config/listener
===============================
Listener
    Address = *
    Transport = HTTP
    Port = 5985
    Hostname
    Enabled = true
    URLPrefix = wsman
    CertificateThumbprint
    ListeningOn = 127.0.0.1, 172.22.13.227, ::1, fe80::5efe:172.22.13.227%12, fe
80::8cf:d5f2:1fab:b2cd%11

==========================



  • I got the above output which is showing us that WINRM is listening successfully.


  • To figure what is the exact issue, i accessed the original server which is facing issue.


  • I initiated the below command to check the listener.



winrm enum winrm/config/listener

 ========================
 Listener [Source="GPO"]
    Address = *
    Transport = HTTP
    Port = 5985
    Hostname
    Enabled = true
    URLPrefix = wsman
    CertificateThumbprint
    ListeningOn = null
============================


  • I got a strange output, which is telling that it is listening to null. Now i checked how this WinRM is configured, when i dig down the cause i came to know that it is configured using GPO.

  • Now i initiated RSOP on this server and observed that WinRM setting
"Allow automatic configuration of listeners" is enabled. Please look at the below event.



And then initiated gpresult /v /scope computer and when i checked the result and came to know that it getting filtered and IPv4 Value: 0,0 is something that not listens to it.


  • Now get back to Group policy and in place of IPv4 filter i have given Asterisk "*" symbol and force updated the group policy on the server.

This done the magic for me, now the WinRM service  was again listening on all IPs.

Reactions:

1 comments:

Post a Comment