Localization of these texts in not currently implemented (commercial customer who requested this functionality did not need localization) and there is no exact schedule when it could be implemented.
Thanks for the information,
In my case, the server in "Source" column in Syslog Monitor exists as a node in NetXMS. However, most of the computers in "Host Name" column do not exist as a node in NetXMS.
I could not manage to find a way to get source computer info from ForwardedEvents in Windows Event Collector Server. Desperately need help.
https://docs.microsoft.com/windows/win32/wec/windows-event-collector?redirectedfrom=MSDN
Hi,
source address for connection is determined only by routing. NetXMS server itself does not specifically select source IP address. If routing is correct then it should work. For network service checks to work you should have "portcheck" sub-agent loaded in local agent (the one running on NetXMS server itself). Make sure that it is loaded. Also you may increase debug level for agent and check what is going on when server requests service check.
Best regards,
Victor
We've managed to replicate similar behavior that could be related to what is happening on your system - when node is removed from template, the .xml does not get deleted from that node. You can follow resolution progress here: https://track.radensolutions.com/issue/NX-1704
