1

Having some trouble getting spiceworks to scan pfSense via SSH.

I’ve set up a spiceworks user on pfSense with System-Shell account access, can login to it via Putty just fine.
In the “enter new credentials” prompt on Spiceworks (SSH Login Failures screen), it logs in fine, go to re-scan, and it gets thrown back into SSH Login Failure.

I do get the following from the pfSense logs:

Oct 2 23:42:53	sshd[82951]: Accepted password for spiceworks from 192.168.2.57 port 52079 ssh2
Oct 2 23:47:42	sshd[84500]: Did not receive identification string from 192.168.2.57

I’ve done some searching around, most recent stuff I can find on this is from 2007-2009ish, but no resolution.

Anyone else have this working, and if so can point me in the right direction?

@Spiceworks @pfSense

2 Spice ups
2

Also,

I’ve tried logging in as admin from spiceworks just to see if that resolves it.

pfSense reports:

Oct 2 23:58:42	sshd[21056]: Accepted password for admin from 192.168.2.57 port 52377 ssh2

<-- after spiceworks' timeout -->

Oct 2 23:59:46sshd[13109]: Timeout, client not responding.

Spiceworks reports:

Connection timeout. Make sure SSH is running on 192.168.2.119

=\

3

I believe I followed this tutorial ( http://community.spiceworks.com/how_to/show/2042-setting-up-a-pfsense-2-0-or-greater-ssh-account-for-spiceworks ) when setting up mine o be scanned by Spiceworks.

1 Spice up
4

You could also enable SNMP community or Private strings to scan more information.

5

Are you trying to use the admin account for the ssh or did you setup a specific account for Spiceworks?

6

Tried both. Admin times out on spiceworks even though pfsense says it logged in fine. Spiceworks account (set up on pfsense) logs in on both, but then gets error on re-scan and asks for new credentials.

7

SNMP is enabled, but it wasn’t getting anything from it. Removed device, added custom scan range, re scanned and it scanned it with snmp just fine.

I really think I need to just go to sleep and wait until the morning to post things when I’m up this late.

Will check if it’s able to scan via ssh in the morning…

1 Spice up
8

Derrick, Have you got this figured out? Any additional attempts to set this up? Are there any errors about failed login attempts in the pfSense logs during the scan time?

9

Haven’t had the chance to check back up on it yet. Will try to get to it this evening and report any findings/updates/fixes.

10

I had the same problem… I ended up using “root” instead of admin and it finally took it.

11

yes it works @kvnetfx. Used root as username and password that of admin.