Discovery credentials issue with my Windows 10 host

[Valon Sheremeti]

Hi all

I'm having an issue testing Discovery credentials with my Windows 10 host.

Windows 10 is the same host where MID Server in configured/running. I read some comment this approach usually fails and I was wondering if there is a way around this issue?

My MID server is properly configured and both Windows Service and MID Servers are running on both Windows and ServiceNow side.

When I click "Test Credential" it comes back with the following

Credentials I have provided are local user admin account named "Valon"

MID Server is successfully registered and validated in ServiceNow instance

[Alberto Consonn]

Hi,

I would suggest you to check in deep the following threads:

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

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

You will find a way to troubleshoot your issue and find a solution!

If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

Thank you

Cheers
Alberto

[Rick54]

Hi Valon,

1. make sure to prefix the domain name if exist.

2. Try the credentials to remote the host before trying via ServiceNow.

[Valon Sheremeti]

This is an update to my own post:

I am successful to running discovery on ALL Windows Servers  lab and I am failing to run discovery to ALL Windows 10 hosts on my lab.

Is there something specific missing on Windows 10 that Windows servers have? I.e. Specific Service or feature that needs enabling?

Credentials are identical; all Windows servers and Windows 10 have same username 'Administrator' and share the same password. Also they share the same IP range. Now the only issue I see is authentication, but I can't figure out what are my Windows 10 hosts missing??

Any thoughts?

[chuckm · Accepted solution]

Validate the WMI ports between the MID Server and the Windows 10 hosts are open (including firewall on the Windows 10 host).  Port 135 from the MID Server to the Windows 10 host must be open for initial communication AND high ports 49152 - 65535 must be open for the remainder of the communication.

Different high ports are required to be open depending on the Windows OS Version.  For example, ServiceNow discovery initiates communication to Windows Server (2000, 2003, and XP) on port 135 from the MID Server to the Windows Server AND completes the communication using high ports 1025 – 5000.

ServiceNow Discovery Windows High Port Ranges Based on Operating System:

Port Ranges:  49152 – 65535 (Windows Server 2008 and later versions, and in Windows Vista and later versions)

Port Ranges:  1025 – 5000 (Windows 2000, Windows XP, and Windows Server 2003)