Mid server discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2023 10:49 AM
Hey
I am having issues where the mid server discovers some devices and some aren't.
For example -
Consider a site having multiple devices such as network devices / windows machines / handheld devices.
From which all the network devices are getting discovered. However have issues when discovering the other devices.
Any help would be highly appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2023 01:35 AM - edited 03-27-2023 01:36 AM
Hey Pratik
All firewall rules were checked and also the credentials everything checks outs. I see there was another person facing the same issue.
Your advice is highly appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2023 01:50 AM - edited 03-27-2023 01:50 AM
Hi Eshan,
The error code is generic if u search on google.. This can happen due to multiple reasons.
1. Test the port connectivity-
Like for Windows its 135-139. Also u can validate using wbemtest command from your MID server to target server whether WMI session is working or not. You also mentioned that its discoverable from another server- did u verify if the subnet is same of that server and the MID server? If same subnet then i would recommend checking the the above steps and also the local firewall and group policies... Often the culprit is policies pushed OR service account not given right privileges...
Also what is creds test showing in ServiceNow and what does it show in the logs when u try to run a quick discovery?
2. For Network, u cannot test using telnet. Test the creds from ServiceNow first, if its failing then you need to check the logs using WireShark to confirm if traffic is reaching or not.
