Discovery error-No results returned from probe

[salu]

Hello all,

Can someone please help me to understand this error?

[adilrathore]

It seems that you have not opened the appropriate ports to scan. Which device type is it, Windows, Linux. Switch?

[Henrik Jutterst]

Don't know if you've solved it, but since there's nothing marked as a solution my question to you is if you're using any non standard ports? If Yes, have you defined them in IP Service table for the CI type? Maybe SSH is not running on port 22 for you, for example.

[Aishwaryaaa_]

@salu have you resolved your errors about discovery schedule? if yes then please help me out I'm also facing the same errors while scheduling the discovery.

[Community Alums]

Any answers for this

[Henrik Jutterst]

I just ran into this warning again and in my case this was due to Firewall blocking SSH traffic from MID server to the hosts.

Hope that might help future questions regarding this message: "No results returned from probe"

I also found this KB with some additional help - for other reasons: KB1002071
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1002071