Discovery error : IOException - An existing connection was forcibly closed by the remote host

geet
Tera Guru

Hi,

I am trying to run Quick Discovery for an IP and getting the following error in shazzam probe.

<results active="1" alive="1" probe_time="7502" result_code="0" total="1">
<result active="true" alive="true" ip_address="13.107.246.51">
<scanner name="HTTP" port="443" portprobe="http" protocol="tcp" result="io_error" service="https">
<error_msg>Problem while reading HTTP response: : IOException - An existing connection was forcibly closed by the remote host</error_msg>
</scanner>
<scanner name="HTTPS" port="5986" portprobe="winrm_ssl" protocol="tcp" result="timed_out" service="winrm_ssl"/>
<scanner name="HTTP" port="80" portprobe="http" protocol="tcp" result="open" service="http">
<response_code>200</response_code>
<http_version>HTTP/1.1</http_version>
<response_text>OK</response_text>
</scanner>
<scanner name="SLP" port="427" portprobe="slp" protocol="udp" result="timed_out" service="slp"/>
<scanner name="NBT" port="137" portprobe="wins" protocol="udp" result="unresolved" service="ms-nb-ns"/>
<scanner name="DNS" port="53" portprobe="dns" protocol="udp" result="unresolved" service="dns"/>
</result>
 
find_real_file.png
Please help what could be the cause of this issue.
5 REPLIES 5

pratik0306
Tera Guru

its a port issue. you need to check whether the pre requisites are fulfilled and post that u can first test the credentials and then try to run the quick discovery.

We have got all the default ports opened and then ran quick discovery, but still getting the issue.

https://docs.servicenow.com/bundle/rome-it-operations-management/page/product/discovery/reference/r_...

is credential test working? that will provide an hint whether its port issue or credential issue

Gus1
Tera Expert

This is an old post but we ran into the same issue when attempting HTTP Discovery for NetApp Servers. The issue was an application based firewall rule, we had opened port 443 but the server was responding over port 80. The solution was to open both port 443 and port 80.