No results returned from probe.

[jluisangelgg]

The discovery was running correcly and suddenly it stop working, Now When we run a IP range discovery or quick discovery we get the warning "No results returned from probe" in the Shazzam. this happens with all the servers and devices. The MID Server is on DMZ on a Windows Server 2012 x64.

We excute the telnet to the port 135 with the same user as the discovery uses and it was sucessfull when we excute the telnet the firewall log the request to the target server but when we run the discovery the request is not logged in the firewall.

We also checked that the RCP service is on.

Can someone give help me?

This is the shazzam payload

<results active="0" alive="0" full_range="<?xml version="1.0" encoding="UTF-8"?><discovery_ranges><meta_coll><ip_list><ip>255.255.255.255</ip></ip_list></meta_coll></discovery_ranges>" probe_time="0" range="<?xml version="1.0" encoding="UTF-8"?><discovery_ranges><meta_coll><ip_list><ip>255.255.255.255</ip></ip_list></meta_coll></discovery_ranges>" result_code="0" total="1">

<result/>

<parameters>

<parameter name="agent" value="mid.server. MidServer 1"/>

<parameter name="used_by_runbook" value="true"/>

<parameter name="glide.xmlhelper.trim.enable" value="true"/>

<parameter name="range" value="<?xml version="1.0" encoding="UTF-8"?><discovery_ranges><meta_coll><ip_list><ip>255.255.255.255</ip></ip_list></meta_coll></discovery_ranges>"/>

<parameter name="range_index" value="0"/>

<parameter name="shazzam_probes" value="1"/>

<parameter name="source" value="See Payload"/>

<parameter name="sys_id" value="fde8c730dbd76600dd88fa5aaf9619c1"/>

<parameter name="shazzam_chunk_size" value="100"/>

<parameter name="sys_created_on" value="2016-11-22 21:48:48"/>

<parameter name="used_by_discovery" value="true"/>

<parameter name="state" value="ready"/>

<parameter name="probe_name" value="Shazzam"/>

<parameter name="port_probe_spec" value="<portprobes><portprobe><name>wmi</name><scanner>GenericTCP</scanner><description>Windows WMI</description><conditional>false</conditional></portprobe><portprobe><name>snmp</name><scanner>SNMP</scanner><description>Simple Network Mangement Protocol</description><conditional>false</conditional></portprobe><portprobe><name>ssh</name><scanner>BannerTCP</scanner><description>Secure Shell Login</description><conditional>false</conditional></portprobe><portprobe><name>http</name><scanner>HTTP</scanner><description>Web Servers</description><conditional>false</conditional></portprobe><portprobe><name>wins</name><scanner>NBT</scanner><description>WINS Name Resolver</description><conditional>true</conditional></portprobe><portprobe><name>dns</name><scanner>DNS</scanner><description>Domain Name Resolver</description><conditional>true</conditional></portprobe><portprobe><name>slp</name><scanner>SLP</scanner><description>Service Location Protocol</description><conditional>false</conditional></portprobe><portprobe><name>wbem</name><scanner>GenericTCP</scanner><description>WBEM (CIM)</description><conditional>false</conditional><serviceRegistryQuery querierClassname='SLPQuery'><serviceType>service:wbem</serviceType></serviceRegistryQuery></portprobe><portprobe><name>vmapp</name><scanner>BannerTCP</scanner><description>vCenter Server Appliance Web user interface HTTPS</description><conditional>false</conditional></portprobe><portprobe><name>winrm</name><scanner>HTTP</scanner><description>Windows Remote Management</description><conditional>false</conditional></portprobe></portprobes>"/>

<parameter name="debug" value="false"/>

<parameter name="regulator_period_ms" value="1"/>

<parameter name="regulator_max_packets" value="3"/>

<parameter name="priority" value="0"/>

<parameter name="agent_correlator" value="f9e8c730dbd76600dd88fa5aaf9619c0"/>

<parameter name="HTTP_waitForResponseMS" value="5000"/>

<parameter name="probe" value="eb95df760ab301550015543188996362"/>

<parameter name="sequence" value="1588e0343e80000001"/>

<parameter name="mid.discovery.max_payload_size" value="-1"/>

<parameter name="GenericTCP_waitForConnectMS" value="1000"/>

<parameter name="full_range" value="<?xml version="1.0" encoding="UTF-8"?><discovery_ranges><meta_coll><ip_list><ip>255.255.255.255</ip></ip_list></meta_coll></discovery_ranges>"/>

<parameter name="name" value="wmi,snmp,ssh,http,wins,dns,slp,wbem,vmapp,winrm"/>

<parameter name="mid_range" value="<?xml version="1.0" encoding="UTF-8"?><discovery_ranges><meta_coll><ip_list><ip>255.255.255.255</ip></ip_list></meta_coll></discovery_ranges>"/>

<parameter name="topic" value="Shazzam"/>

<parameter name="queue" value="output"/>

<parameter name="ecc_queue" value="fde8c730dbd76600dd88fa5aaf9619c1"/>

</parameters>

</results>

[Ryan Zulli]

Hi Luis,

have you tried to run a quick discovery against a single IP? if so, what were the results?

Thanks,

-Ryan

[jluisangelgg · Accepted solution]

Ryan ,

Thank you for your response, yes, I tried to run a quick discovery, even I tried to make a mid-server self discovery (127.0.0.0), but the issue was already solved, the cause was that one of the admins cleared all the records in the IP Services Table, I imported those records and the discovery worked again

[Runjay Patel]

Check out this video, it will clear all your doubts and help you to understand Discovery queries in details.

Link: https://www.youtube.com/watch?v=30JbWVsusyE&t=10s&ab_channel=ServiceNowHelpdesk

It help you to understand below points.

• Discovery Overview
• Discovery prerequisite
• Understanding Discovery Phases in details
• Discovery credentials and IP Affinity
• Mid Server Management with Cluster and Load Balancer
• Schedule jobs
• Set up discovery from scratch to end
• Live implementation with real world data.
• Troubleshooting on various aspects
• Many more other issue related to mid server, CIs
• Cloud discovery
• Service Mapping

Please mark reply as Helpful/Correct, if applicable. Thanks!!