Please confirm: On the hosts where you get this error, you're not able to get any working SNMP Sensors, correct?
The "No Response (2003)" SNMP error is quite common, it's usually generated when the device is unreachable, but can still mean that:
- SNMP Traffic (UDP 161) is blocked along the way.
- SNMP Credentials not matching (device/PRTG differs)
- SNMP is disabled on the device. (Usually disabled by default, must be enabled)
- The device implements security features which limit the IP's/hosts which can query it over SNMP. (Tricky when NAT is involved)
Kindly review this extensive SNMP troubleshooting guide:
My SNMP sensors don’t work. What can I do?
You may additionally download our latest SNMP Tester, ideally run it on the PRTG Host (or host of the Remote Probe), and perform the "Read Device Uptime" test against the target device, it will allow you to easily test different credential combinations.
Once you get a valid reply, SNMP is working. You can then go ahead and deploy sensors (make sure that the same credentials/sttings are used in PRTG)
Best Regards,
Luciano Lingnau [Paessler Support]
Add comment