Mid server discovery

[Eshan Judiant]

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.  

[Bibu Punnachali]

For a successful discovery,

1) The MID server should be able to reach the target device using the appropriate port.

Please refer to Shazzam probe, port probes, and protocols

2) Based on the type of device appropriate credential should be created in ServiceNow platform

Please refer to Create and test your credentials

[Eshan Judiant]

Hey 

Thank you for the reply. Your reply was helpful. I was able to do few deep dives on the issue and found that the RPC port which gets assigned once the connection is initiated from the Mid Server is always 49154. 

However 49154 isn't listening on all the endpoints hence the reason why they are not getting discovered. 

Would there be a setting change or a configuration to put in place so that the a listening / working ports gets allocated ?

Please find the image below which would show you the DST PORT allocated.

Hoping to hear from you soon. Thank you in advance. 

[Eshan Judiant]

Hey 

This test was done from the mid server. There doesn't seem to be anything wrong with the credentials as the same is discoverable from another server. 

Your feedback is highly appreciated. 

[pratik0306]

for which class of devices you are facing an issue? Ports will be 1 part of the issue, there could be prob with the account being used and if thats been given required privilege, any local firewall, group policies etc...