I am having problems getting PRTG talking to our new Fortigate firewalls PRTG is installed on a windows 2016 server - we already use PRTG to monitor our switches successfully. The fortigate is configured to use SNMPv3. When I run the SNMP tester on the PRTG server I get a no response error.

04/06/2018 10:47:48 (21 ms) : SNMP V3 04/06/2018 10:47:48 (30 ms) : Uptime 04/06/2018 10:47:52 (4086 ms) : SNMP Datatype: ASN_PRIMITIVE 04/06/2018 10:47:52 (4101 ms) : ------- 04/06/2018 10:47:52 (4109 ms) : DISMAN-EVENT-MIB::sysUpTimeInstance = No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003) ( 0 seconds ) 04/06/2018 10:47:56 (8179 ms) : SNMP Datatype: ASN_PRIMITIVE 04/06/2018 10:47:56 (8187 ms) : HOST-RESOURCES-MIB::hrSystemUptime.0 = No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003) ( 0 seconds ) 04/06/2018 10:47:56 (8194 ms) : Done

Any ideas what I am 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.

Dear AlienCowboy,

the error "-2003" can be caused by

  • using the wrong device address, so the target device does not respondo
  • or wrong SNMP credentials (like encryption method, key, port number and so on)
  • or by a device which responds not in time, or not at all

In order to isolate the issue, you could check if the device also supports SNMP v2c and try to get a v2c connection first, before you go for the v3 connection.


Jun, 2018 - Permalink

Ahh yep that fixed it. The fortigate was capable of vSNMP v3 but the windows 2016 server doesn't seem to be.


Jun, 2018 - Permalink