SNMP ERROR# 2003

If you scan against the OID you want to use with the custom sensor using the SNMP Tester does that work?

Yes, that OID is working fine with SNMPTester. Moreover, its not actually for one particular OID, its with all SNMP Sensors(their respective OIDs).

FYI, I am using PRTG V7 with Enterprise Unlimited Edition.

My Opinion:

1. Does it has something to do with SNMP Service and Trap destinations defined on Machine running PRTG.
2. Can you please mail me the checklist(prerequisites) of configuring PRTG for SNMP monitoring?
3. If I have Probe and Server running on same Machine, then are there any Port issues related to them?

Please take me as a beginner and ignore I am silly.

Warm Regards, Nutan

Are you wanting to monitor SNMP traps? In such a case you would need to use the SNMP Trap sensor, not the standard SNMP sensors. See: How can I use PRTG’s trap receiver and what are its limitations?

As to your queries:

• 1. No. PRTG merely reads the value from the SNMP-compatible device. Of course the necessary information (including port, community string, etc.) need to be defined properly for the device in case.
• 2. There are no prerequisites except that SNMP is configured and turned on at the device's end. If the SNMP Tester can access these values, so should PRTG.
• 3. Not really.

No, I dont want to monitor traps, It was just a question pinching my brain.

So, Enabling SNMP is not at all mandatory on the device running PRTG (Running both PRTG Core and Probe).

I tried Adding a SNMP trap reciever too....jst in case if it could work..but bingo...............It didn't...Silly I am.

I also tried it after restarting my PRTG Core Server Service and Probe service... but its not working.

Also,

In the post you have mentioned that Trap Sensor is to be added in local probe, but I found that No Sensors can be added to local probe from WebGUI however we can add sensors to probe device. If there is a way then plz suggest.

I also consider it safe to run probe on 127.0.0.1 rather than on Ethernet Interface IP.

PLEASE SUGGEST SOMETHING, SO THAT I ENABLE MY SNMP SENSORs START WORKING....

On first installation they all were working fine. I don't know what happened to them NOW........

Regards,

Mr Patrick,

Good Afternoon..!!

No, I am not trying to monitor SNMP Traps. What I want is very much simple.

I have READ ONLY community strings of Network devices. I just want to use them for monitoring them as per Default profiles defined in PRTG (SNMP Based).

I am running both Probe and Server on same machine (Win XP SP2).

Probe Administrator Configuration: 1. Server Connection : Connect to loacl core server (via 127.0.0.1 and port specified below : 23560)

2. Probe GID: {Some value}

3. Outgoing IP for monitoring requests: auto

Server Configuration:

1. Web Server : NIC (eth) 's IP (10.x.x.8) Port: 8080 2. Core Server : IPs for Probe connections: Localhost only (127.0.0.1)

No Firewall blockage or any kind of Community string issues. All is fine..

BUT SNMP SENSORS ARE NOT GETTING UP...............!!!!

Please Help....... I beg....for Gods Sake..PLEASE HELP..

please open a support ticket we might have to do a remote session to take a look at this together

send mail to [email protected]

Try to add UDP 161 and 162 to your firewall exceptions. works perfectly for me. Windows XP SP3 and 7

Please see also the article My SNMP sensor don't work. What can I do?

In general, the SNMP error #2003 often hints on problems with basic requirements such as access to ports, authentication, disabled SNMP, etc.