WinRM discovery for windows server is throwing error and the credential gets timed out.

Ayush10
Tera Contributor

Dear All,

 

We are trying to configure and discover Windows server using WinRM over WMI.

The below parameters are enabled on the Mid Server :-

mid.windows.management_protocol - WinRM

mid.powershell_api.winrm.use_ssl - true

mid.powershell_api.winrm.remote_https_port - 5985

mid.powershell_api.winrm.remote_https_port - 5986

 

MID Server Properties:-

glide.discovery.windows.use_legacy_wmi- false

glide.powershell.use_powershell - true

mid.use_legacy_wmi - false

 

When we are trying to run the test the credential from ServiceNow instance we are getting "credential timed out error".

As part of testing , from Mid server to the host the Enter-PS Session is running successfully and Test-WsMan command is also running successfully.

The error found in logs is -

response code 404 over port 5985 over winrm protocol.

PowerShellSessionPoolKey[target:X.X.X.X&port:135&fixed_cred:&tag:&type:winrm&noCredFallback:true&configurationName:]

 

Expedited:MultiProbe-X.X.X.X) [MIDPowerShellUtils:118] 2026-06-21 14:02:34 Running test script: test-wsman -computer X.X.X.X -port 5985 -ErrorAction stop

 

 

Kindly provide some input if anyone has implemented WinRM for discovery of Windows server

0 REPLIES 0