Hello everyone,
I recently upgraded our Spiceworks installation from version 6.2 to 7.0, and I am experiencing some troubles with some of our SNMP devices.
Our local router/firewall works fine, but some firewalls and printers can no longer be scanned.
When I run snmpwalk from a GNU/Linux host, it works just fine, but Spiceworks says it cannot scan the devices in question.
I’ve already tried disabling the firewall - temporarily, just to check if it helps - without success. When I run Wireshark while trying to scan the devices from Spiceworks, I see no packets at all going to or coming from the targets.
Spiceworks is running on a Windows Server 2012, if that matters.
Has anyone experienced similar problems, or does anyone have an idea how to fix this?
Thank you very much for any suggestions!
2 Spice ups
i’m having problems with scanning devices on my network via IP addresses since the upgrade to 7.0
mattbartle
(Matt Bartle)
3
Have you tried going to the scan errors page and trying to fix them by re-entering the SNMP credentials? This sometimes works, even if you have already entered the exact same credentials before.
@Matt: Thanks for the hint! It still does not work, but by now I have pretty much given up and resorted to managing the devices manually (which basically means entering some information and then leave them alone - for monitoring I use Nagios, anyway).
In case it matters: The most recent update to spiceworks did not help either. 
mattbartle
(Matt Bartle)
5
Did you try both SNMP and SNMP v2?
As far as I understand, Spiceworks tries SNMP with the community string “public” on its own, so I only tried SNMPv2. At least it told me so, when I tried to use SNMP with “public” manually.
Thank you very much for your replies - the most recent update to Spiceworks seems to have done the trick, plus one printer that Spiceworks had trouble scanning has been replaced, and now everything works the way it is supposed to. 
