Discovery Warning - Socket Error

Stephen Skaggs · ‎11-16-2020

Receiving multiple warnings that contain the message: socket error

I have searched the web and could not find a solid answer to this.

Rahul Priyadars · ‎11-16-2020

here is what do you mean by Socket error:-

A socket is bound to a port number so that the TCP layer can identify the application that data is destined to be sent. ... A socket error can occur if one or more of the above conditions are not met or something is blocking communication between the client and server (e.g. firewall, anti-virus).

It has something to do with Communication PORT as mentioned in above POST.

How to Test PORT issues and trouble shoots for PORT and Credentials-

https://hi.service-now.com/kb_view.do?sysparm_article=KB0657528

Regards

RP

View solution in original post

tim_broberg · ‎11-16-2020

That's not terribly helpful, is it?

There should be a probe associated with each of those messages, I believe. The ecc_queue input?

If you find the ecc_queue output associated with those inputs.

You should be able to see details on the command executed there, like the ip / host name of the target server.
If you search the agent/logs/agent0.log.* files for the sys_id of that ecc_queue output record, you may find additional details.

- Tim.

Stephen Skaggs · ‎11-18-2020

Thanks for the reply, the logs really did not show me anything regarding the socket error.

Vivektietsood · ‎11-16-2020

A "socket error" indicates that data sent over the network has not arrived in time.

Please start with checking that you have firewall ports opened from mid server to target devices you are trying to scan like 135 for WMI Windows or 22 for SSH Unix

Stephen Skaggs · ‎11-18-2020

Thanks for the reply, working with network team to determine if that is the issue.