Good morning

We have a single core PRTG server with several remote probes installed on servers behind routers and firewalls on separate subnets.. We have around 700 sensors all working fine (monitoring things like SQL databases, services, server memory & HDD space etc) but when I add SNMP sensors they always fail to connect.

If I add SNMP sensors to devices on the same network as the core server everything works as it should do.

My question is that, even with a remote probe installed on a remote server, do I need to open port 161 (and 162?) on the firewall to allow SNMP communication with the core server?

Many thanks, Mark

Article Comments

Dear Mark, no, the target does not need communicate with the Core Server but with the Remote Probe. Therefore you do not need to open SNMP ports between the Core and the Remote Probe site.
You just have to make sure the machine running the probe can communicate with the target device.
Best regards


Jul, 2013 - Permalink

This doesn't seem to be an issue with the core server, respectively the connection therewith. One possibility, however, is that the IP address for the remote probe is not allowed to connect with the target device. Please run our SNMP Tester v5 Beta on the probe machine and try connecting to the device in case (e.g. by running an "Uptime" or a "Walk" test). Does this yield any results?


Jul, 2013 - Permalink

Hi both and thank you for your replies.

In this case the remote probe is installed on the target server we wish to monitor. It is a Dell server and we wish to use the SNMP hardware monitoring functionality of PRTG. The fact that the remote probe is installed on the same server as we are trying to monitor should mean this would work, wouldn't it?

Patrick - I have run an uptime test using the tester you suggested on the target server and it works fine.


Jul, 2013 - Permalink

Please also run a "Walk" test using base OID 1.3.6.1. Then, please forward us the resulting log file to support@paessler.com, with reference to this thread.


Jul, 2013 - Permalink

Patrick

I am not clear what information needs to be entered into the "Walk" box - could you advise?

Thanks.


Jul, 2013 - Permalink

Merely enter 1.3.6.1 and run the walk. This should yield a list of resulting OIDs that are available on the device. Please forward us this list.


Jul, 2013 - Permalink