Not able to validate credentials
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2023 04:59 PM
Experts,
I am trying to validate credentials on Windows 10 Laptop from a MID server [Windows 2016]. Both are on same network. But I am still unable to validate credentials. I am on Tokyo version .
1) Firewall is disabled on target host
2) Ping from MID server OK
3) Telnet from MID to target host OK
4) From MID server Power shell command ==> gwmi win32_operatingsystem -computer 192.168.1.212 -credential 'svcacct_discovery' FAILS
Not sure what is the reason?
Any other point I should be checking?
Please advise.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2023 07:33 PM
Is the computer in a domain?
If yes , try to add the domain to the user name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2023 03:38 PM
@newhand I tried with domain name as well but still no luck.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2023 07:46 PM
From MID server Power shell command ==> gwmi win32_operatingsystem -computer 192.168.1.212 -credential 'svcacct_discovery' FAILS ---> Means WMI needs higher ports also for communication please check those too.
=====
ServiceNow Discovery uses WMI for discovery, therefore port 135 from the MID Server to the Remote Windows host must be open for initial communication AND high ports 49152 - 65535 must be open for the remainder of the communication.
=====
Hope this helps
Windows Credential
A simple Powershell WMI query directly from the MID Server to the remote machine can be used to test access and permissions.
Open a PowerShell command line on the host where the MID server is being used and run the following:
gwmi win32_operatingsystem -computer 192.168.200.14 -credential 'LOCALDOMAIN\mid'
Substitute LOCALDOMAIN\mid by the credential to test, and 192.168.200.14 with the target IP address. The expected result would be similar to:
SystemDirectory : C:\Windows\system32
Organization :
BuildNumber : 6001
RegisteredUser : Windows User
SerialNumber : 12345-OEM-1234567-12345
Version : 6.0.6001
If the WMI command above fails, either the credential is incorrect or lacks permission. We advise your windows admin team to further investigate the issue. If basic WMI queries from the MID server to the target hosts fails, then discovery and orchestration activities would not be successful.
Regards
RP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2023 03:37 PM - edited 02-24-2023 03:39 PM
Hello @Rahul Priyadars ,
I checked all of these but nothing seems to be a problem from there.
I also followed below document which is typically for Windows 10/11 system, and followed all these steps, still no luck.
Network Computers are not Showing Up in Windows 10/11 | Windows OS Hub (woshub.com)
Any other tip do you want to suggest?
Thanks.