SNMP Library Sensor SNMPERR_BAD_SENDTO (SNMP error # -12)

Modified on 2025-06-10 13:38:08 +0200

I downloaded an MIB file that I converted using the MIB Importer and then copied it to the appropriate directory in PRTG. Everything went smoothly with the MIB importer and there were no errors.

When I attempt to create an SNMP Library sensor with the newly added file, I get the following error: SNMPERR_BAD_SENDTO (SNMP error # -12).

I have an SNMP Receiver setup on my probe device and I show records coming in successfully but I am unable to use this library. Any thoughts on what I may be doing wrong?

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

This error usually appears if SNMP Requests are sent to the wrong targets. Please check the "Outgoing IP" for monitoring requests in the PRTG Probe Admin if it's correct, and maybe try re-setting it anyway.

Aug, 2014 - Permalink

Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

SNMP Library Sensor SNMPERR_BAD_SENDTO (SNMP error # -12)

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.