Active, couldn't classify: No WMI connection, now finished

[sukran]

We got an error for some windows devices as below in the WMIRunner / WML Classify

<result><error>Failure(s) with available Windows credentials from the instance.</error><error>The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)</error></result>

While did a test in ' test credentials and it has been successfully validated , how to figure out this

[sukran]

Hi chuckm,

I checked with window server team , they said port 135 has communicate with mid server but ( high port 49152-65535) couldnt 

alos they pointed out telling other server which is discovered as expected but this server also same scenario like ( high port 49152-65535 ) in not communicating 

how to deal this

[chuckm]

sukran,

Are both Windows hosts using the same version of windows? I didn't provide the high ports for older versions of Windows, because most organizations have since upgraded. The high port requirements are different for different versions of windows as follows:

High Ports 1025 - 5000: Windows 2000, Windows XP and Windows Server 2003
High Ports 49152 - 65535: Windows Server 2008 and later versions, and in Windows Vista and later versions

Is it possible to open the high ports temporarily to test Discovery? That way you could eliminate this as the issue and move on to troubleshoot other areas. The key is that for ServiceNow Discovery to discover Windows servers - it uses WMI which uses port 135 for initial communication and the high ports for the remainder of the communication.

[monica12]

Hi , i am facing a similar issue, what did you do to resolve it?

[sukran]

95 % - windows firewall is blocking 

5 % - System issue , so you can go to ecc queue-> open shazzam out put -> delete ( processed , created and sequence ) and state change to ready 

and insert and say , it will run the job again to update

Mainly its firewall blocking issue 

[Ashutosh Munot1]

Hi MOnica,

I will always start looking into this issue by going to MID server and following this article:

https://community.servicenow.com/community?id=community_question&sys_id=e99c03e5db9cdbc01dcaf3231f96...

https://community.servicenow.com/community?id=community_question&sys_id=094970fedb07b3c8d82ffb243996...

https://hi.service-now.com/kb_view.do?sysparm_article=KB0549834

Start with looking by running this command from mid server to target machine:

gwmi win32_operatingsystem -computer 192.168.200.14 -credential 'LOCALDOMAIN\mid'

Thanks,
Ashutosh