SNMP Timeout: No Response from error due to client missing community string

Issue

SNMP host not reporting data.

Tests on one of the systems with this issue:

# snmpwalk -Os -c MyCommunityName -v 2c localhost iso.3.6.1.2.1.1.1
sysDescr.0 = STRING: Linux server2.redhat.com  2.6.32-504.12.2.el6.x86_64 #1 SMP Sun Feb 1 12:14:02 EST 2015 x86_64

# snmpwalk -Os -c public -v 2c localhost iso.3.6.1.2.1.1.1
sysDescr.0 = STRING: Linux server2.redhat.com  2.6.32-504.12.2.el6.x86_64 #1 SMP Sun Feb 1 12:14:02 EST 2015 x86_64

# snmpwalk -Os -c  MyCommunityName -v 2c 172.22.88.13 iso.3.6.1.2.1.1.1
Timeout: No Response from 172.22.88.13

# snmpwalk -Os -c public -v 2c 172.22.88.13 iso.3.6.1.2.1.1.1
Timeout: No Response from 172.22.88.13

In this scenario, the SolarWinds application is on a remote host (not the localhost) to capture the SNMP information.

The SolarWinds box is sending a "null" for community string on the non-working hosts

Although, this solution is not necessarily specific to using SolarWinds.

Packet Capture:

30 24 02 01 01 04 - 00 (community string - 0 bytes long - ie null)

A0 1D 02 02 - 54 6D - 02 01 - 00 - 02 01 - 00 

30 11 30 0F 06 0B - 2B 06 01 02 01 19 02 03 01 03 1F - 05 00