- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2019 07:39 AM
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
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2019 03:05 PM
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)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2019 03:28 AM