Main problem is to find Linux ODBC driver for MS SQL. Second is to configure unixODBC.  There are some useful links from unixODBC site: http://www.unixodbc.org/odbcinst.html http://www.unixodbc.org/config.html Please note that FreeTDS mosy likely will not work because it doesn't support UNICODE ODBC interface. Best regards, Victor

Wow quick response! Thank you once again!

Thank you, that would make netXMS even better 

Thanks Victor!

Example 1: On one of the servers I'm monitoring (internal netwerk, just like example 2) the status check gives back a "4" when it goes offline. When I put it back online, netXMS doesn't notice this change, I can manually poll it, edit the config through netXMS . What can be causing this? There is no firewall and no significant change since last time it worked  ??? /EDIT On a workstation I've just added, this is working fine ??? I am getting confused. /EDIT2 I had a rule up in the event policy editor that said the following: Source: [Computername] Event: SYS_IF_DOWN ALARM: [Hardcoded text] ACTION: [Send email] Source: [Computername] Event: SYS_IF_up ALARM: [Hardcoded text] ACTION: [Send email] When I deleted this rule, deleted the node and added the node again, everything worked perfectly, what am I doing wrong? Example 2: One of the printers with SNMP support i've added, when it goes offline it does not notice that the machine went offline, nor does it notice when it goes back online.  All the other DCI's via SNMP seem to be going properly and  they don't give any errors. /EDIT This node also has the "netXMS NAT adapter" listed as a network connection for some reason, can't find it in the documentation. Could this be the reason?? I'm using the 0.2.20 console, server and agent.

Thank you for the help, don't ask me why but it's working now after I've started from scratch, must have made a typo somewhere.

@victor said in Agent bug?: It looks more like bug in a server, not in agent. As a test, can you check if it is possible to collect same DCIs using command line, like this: nxget server_address System.CPU.LoadAvg Best regards, Victor I got back Configuration file OK  nothing more, nothing less.  Not sure if this is good or not  ;D

Hello! You can call external commands from agent by creating new parameters with ExternalParameter configuration option. As an external command you can use cscript to run your vbscripts. Agent will return first line of script output as a value of parameter. You can also look at this topic for some examples of ExternalParameter usage: https://www.netxms.org/forum/index.php/topic,255.0.html Best regards, Victor

It depends on your environment and requirements, but here are some of possible advantages: * Centralized configuration - you can change configuration of agent from management console; if needed, you can even store agent configs on NetXMS server * More secure: communications between NetXMS server and agent can be encrypted, additional authentication on agent can be configured * TCP instead of UDP is used for communications with agent - this can help in case of slow and poor quality links * Remote command execution - agents can be used to execute commands on managed systems as a reaction to certain events * Proxy functionality: agent can be used as a proxy to reach agents on hosts not directly accessible by NetXMS server * SNMP proxy: agent can be used as a proxy to reach remote SNMP devices * Extensible: you can add new parameters very easy using ExternalParamer configuration option or by writing your own subagents * Easy upgrade - you can upgrade all agents at once from console Best regards, Victor

Hello! It's looks like a bug... I'll check it. Best regards, Victor

This topic has been moved to Feature Requests. /topic/272

I upgraded this morning to v2.20 on server and on 1 client. Only upgrading the server didn´t solve the problem. MAC addresses were still 00.00.00.00.... I had to upgrade the NETXMSclient on the machine reporting blank MAC address. And worked fine. Seems to be a problem on the client, because even if you manually try to pool "Status", "Configuration" or the new option "interface names" doesn´t work. Also, the network interface were appearing as "lan0" and after solving the problem, it detected as "local area connection" I hope these information help you on next releases. PS: I´m still with the problem on SNMP devices. I´ll take look and try to find out an answer. Thanks !

Using Filemon, I found out that the nxav.exe is trying to access the following path : C:\Documents and Settings\<user>\Application Data\nxav-00000E04 And is getting "path not found" I could notice that this folder is only created when the nxav.exe is running. if you close the Alarm Viewer, this folder is deleted. There´s all the icons inside this folder, but I don´t know why the executable isn´t finding it. Just FYI .

@victor said in Vista x64 console bug: Hello! Yes, this is known problem and it is fixed in 0.2.20. Best regards, Victor Thanks for the quick response 

Hello! Consoles from RC will not work with final 0.2.20 - you will have to upgrade installed consoles. Otherwise it is compatible - i.e. you can use standard upgrade procedure to upgrade RC3 to final release. Best regards, Victor

Hello! Now, recovery procedure can be following: Delete database netxms_db. Delete SQL user netxms if it's exist (under Security -> Logins). Ensure that you have mixed mode authentication: in SQL Server Management Studio right click on server object, select Properties, select "Security", and ensure that under "Server authentication" selected "SQL Server and Windows Authentication mode". Reinstall NetXMS, and when on database configuration tab, enter any random password for database user "netxms". Best regards, Victor

@prutser said in Oracle Login Check: However maybe 1 question. It seems that when i want to edit the etc/nxagentd.conf, to reflect the changes, I hav to restart the agent service. Is there another way to reflect the changes in the config file? No, agent should be restarted to load updated config (at least now). However, if you edit agent's config from management console (right click on node -> edit agent configuration), there are an options to "save" or "save and restart agent". To use this feature agent should have write access to config file and server's IP should be in ControlServers or MasterServers section of agent's config.

When you create a node, system automatically creates DCI called "Status". This DCI polled once per minute and contains node's status. You can find collected data in idata_xx tables, where xx is node's id. Best regards, Victor

Hello. Unfortunately, https is not yet supported (oh, it was planed months ago…). As temporary workaround — you can use either external script (with something like curl https://... | grep "keyword | ... ) or setup something like stunnel and configure sevices in netxms (check Victor's link for that). However, I'll try to put encryption on a schedule for upcoming 0.2.20.

It's not documented yet