How to discover on the PORT like (135,22,80,443) in SNOW

[AJ63]

Hello All,

We are doing having issue for port level discovery, where SNOW should discover all the devices which are open in particular port which should be given some where.

Is there any way to achieve to this?

********Urgent**********

Regards,

AJ

[robertgeen]

Hello AJ,

This is hard to answer without more information. What are trying to achieve? Is it possible to give us an example? It's hard to tell if you are talking about TCP/IP communication or initial discovery. Thanks.

[AJ63]

Hello robertgeen,

Thanks for your reply on this and sorry that it did not gives you sufficient info to answer.

So here we go...

We are planning to have discovery set up in S-NOW and the req'ment is to discover thing on the basis of PORT....

Ex: Client will give full range of IP Address and ask us to discover devices on the basis of ports like

                  If client say set a discovery for PORT 135 or 22 or 80 or 443 and get all devices where port is defined as 135 or 22 or 80 or 443.

Is this possible to do from Service Now?

-AJ

[robertgeen]

Hello AJ,

So I think what you are asking is to only discover infrastructure that have certain ports open instead of everything correct? I'm not entirely sure it would be possible without customizing how discovery works to tell it to only run discovery on hosts with those ports open and the reason for this is that the Shazzam port probe is scanning for the purpose of finding common ports used by technologies that can be used to run discovery. It's not really trying to limit based on a list of ports as much as it's trying to say "I know I can run discovery using XYZ if I see ABC open on the infrastructure". The best thing you could do would be to play with the Port Probes and limit it only to the ports that you want and attach them the discovery methods that are available and see if that helps.

If they happen to be running custom ports for things like SSH and WMI then port probes would also be the way to go about adding those custom ports to the discovery process so that it tries to connect on them. I hope this helps.

[doug_schulze · Accepted solution]

Robert,

Even simpler he can just use a behavior that defines exactly what ports should be checked during a discovery!