I have changed the Ip address of one of my devices and all the sensord say "No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (erreur SNMP # -2003)"

Article Comments

Please make sure to check if:

  • The new ip you just entered is correct
  • The other device is available in the network (the system that is running your probe needs to be able and allowed to send udp requests to that target and receive the answer)?
  • The snmp service running on the second device and must be using the same configuration as on the old one (snmp version and community string)

Jul, 2013 - Permalink

The new IP is correct , same Vlan than the probe. All the sensors of the device ( debian server) were responding fine until I change the IP.

PRTG version 13.1.1.1182


Jul, 2013 - Permalink

So you changed the ip of the system and you changed the ip in the device settings in prtg, is that correct? Does the probe system have an ip address in the same subnet als the target system?


Jul, 2013 - Permalink

Yes it is correct. And yes.


Jul, 2013 - Permalink

Can you snmpwalk locally on the Debian server and it returns successfully?

snmpwalk -c public -v 1 127.0.0.1

That would be the first step. If it doesn't work locally, that is the problem...review the snmpd.conf, firewall/iptables, etc.

If it does work, then use the Paessler SNMP tester from the PRTG probe to see if that works. Go from there.


Jul, 2013 - Permalink

Randolfini has got a point. We'd like to add, that you can also use the Paessler SNMP Tester for the local walk. With the v5 of the Tester we added the possibility to perform snmp walks. If you only want to know if your SNMP is responding at all, you could also use the option "Read Device Uptime". Its very highly unlikely that the system uptime is not available on a system that supports snmp.


Jul, 2013 - Permalink

Any update Jean-Jacques?


Jul, 2013 - Permalink