NetXMS Support Forum

It shouldn`t change anything, it was just a guess .
Could you let me know which Linux distribution you are using, what kernel etc... Also, which version of Windows?

Could you try changing the PING subagent section in config to uppercase? As in:
*PING
DefaultPacketSize = 46
...

Could you, please, provide the output of "nxagentd -C"? Don`t forget to edit out any sensitive data, I am interested specifically in the PING subtree.

Ok and is there anything in the log similar to this line: "Unable to add ICMP ping target from configuration file."?

Could you please verify that the PING subagent is in the list opened by Right click on pinging node -> Tools -> Info -> Agent -> Subagent list. And that you get this entry in your agent log once it is started:
*I* Subagent "PING" (ping.nsm) loaded successfully (version 2.2.1-14-g375721606)

Is the pinging node connected via a tunnel or directly?

Hi!

Could you explain in detail how are you trying to achieve the values. Are you using a different source node for the DCI`s and are you using any scripts?
I have tested on Linux with the same configuration and everything seems to be working...

Regards,
Eriks

Unfortunately, it does not support table DCI`s yet.

Regards,
Eriks

Unfortunately this is not currently possible...

Regards,
Eriks

You can disable the "Modify" object access right for the specific map and enable only the "Read" object access right. This will disable the possibility for the user to save any changes for the map. However the user will still be able to change the layout for the map, but once the map is closed and reopened, the changes will be reset.

Regards,
Eriks

Hi!

Your user or group needs to have the "Register agents" access right in order to access the Agent Tunnel Manager.

Regards,
Eriks

You can find it in the Access Rights property page of the object you are trying to access

Hi!

You could be having the same problem as this user - https://www.netxms.org/forum/configuration/snmp-walk-access-denied/msg23267/#new. See if this helps!

Regards,
Eriks

Hi!

This is a known bug which is fixed in our development branch. Once the next release is ready, it will include the fix also.

Regards,
Eriks

Hi!

New access rights for reading object data were introduced in 2.1.2. Check if your user/group has the Read SNMP data access right for the object you are trying to access!

Regards,
Eriks