Socket error. Make sure SSH is running on

cyberconsecurity · 2010-12-26T08:56:39.000Z

I have seen many similar post but no solutions to the "Socket error. Make sure SSH is running on" . I am running the latest version of Spiceworks and can putty into it with no problem. It is a debian Linux system, I have other Linux systems with the same user name and password and I can inventory them correctly. The only difference is this latest system is running the latest version of Debian. Not seeing anything in any off the connection logs and there is no firewall running on the system either.

Thanks for any help.

bytesnake · 2010-12-27T01:15:12.000Z

Try to define an own scan range for this machine at the top and assign the SSH scan account only. Does this work?

cyberconsecurity · 2010-12-27T04:47:02.000Z

That did it, thanks for the help. Wish all problems were this simple to fix.

bytesnake · 2010-12-27T04:47:48.000Z

Glad, you got it

Maybe you want additionally follow at least #1 - #3 of this how-to: Troubleshooting Spiceworks Inventory Inconsistencies - Spiceworks … (if not already done)

richarddepas8602 · 2011-04-22T09:25:20.000Z

I tried setting up a dedicated scan but it did not correct my issue. Initially when I was doing a full range scan, it was seeing the web interface on the ASA. When I dedicated a scan, it now sees it differently, but will not log into it even though I can use PuTTY and get right in with SSH v2 with same credentials I have setup in SpiceWorks.

trnty5264 · 2011-06-22T14:48:10.000Z

That dedicated scan solution fixed my linux servers. Thanks!