Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - ladz

#1
General Support / Re: Active Discovery on 2.0-M4
June 25, 2015, 07:43:47 AM
Hi,

at first I had no filter. And I also tried to setup filter only for subnet 192.168.11.0/24. But situation was the same in both cases.


Ladislav
#2
General Support / Re: Active Discovery on 2.0-M4
June 24, 2015, 12:41:39 PM
Hi,

version 2.0-M5 partly helped. I checked log and server found nodes from subnet 192.168.11.0/24 (but every node has MAC 000000000000  - ?) , but the server didn't add them to NetXMS

Thanks

Ladislav
#3
General Support / Re: Login to server
June 24, 2015, 12:17:16 PM
Hi,
I updated server to version 2.0-M5 (clean installation with new db) but it didn't help.
I setup debug 6 and I tried to login as admin. In the log

[DEBUG] [CLSN-6] Received message CMD_GET_SERVER_INFO
[DEBUG] [CLSN-6] Server time zone: CET+02CEST
[DEBUG] [CLSN-6] Sending message CMD_REQUEST_COMPLETE
[DEBUG] [CLSN-6] Received message CMD_REQUEST_ENCRYPT
[DEBUG] [CLSN-6] Sending message CMD_REQUEST_SESSION_
[DEBUG] [CLSN-6] Received message CMD_SESSION_KEY
[DEBUG] [CLSN-6] Sending message CMD_REQUEST_COMPLETE
[DEBUG] [CLSN-6] Received message CMD_LOGIN
[DEBUG] [CLSN-6] authentication type 0
.
.

[DEBUG] [CLSN-5] readThread: message receiving error
(MSGRECV_COMM_FAILURE)
[DEBUG] [CLSN-6] readThread: message receiving error
(MSGRECV_COMM_FAILURE)


When I restarted  the server, I could connect without any problem. It means, the problem is persistent.

Thanks,

Ladislav
#4
General Support / Re: Active Discovery on 2.0-M4
June 16, 2015, 11:59:20 AM
Hi,
I setup debug 6. In log was
..
Starting active discovery check on range 192.168.11.1 - 192.168.11.255
Active discovery - node 192.168.11.127 responds to ICMP ping
..
Finished active discovery check on range 192.168.11.1 - 192.168.11.255
..

192.168.11.127 was only one address from subnet 192.168.11.0/24 in log.
But node 192.168.11.127 doesn't exist. For example it exists node 192.168.11.34 but server didn't check it. I tried to ping from server to 192.168.11.127 - no response and to 192.168.11.34 - response Ok.


Thank you

Ladislav
#5
General Support / Re: Login to server
June 16, 2015, 11:43:02 AM
Hi,
LDAP server is OK. I'll wait for version 2.0-M5

Thanks

Ladislav
#6
General Support / Login to server
June 12, 2015, 01:14:29 PM
Hi,

I installed version 1.2.7 and setup LDAP synchronization. Approximately one week everything was OK. Now I can't connect to the server as AD user nor admin (nxmc). I restarted the  server and I could connect to the server again but only for 30-60 minutes. There was no error in log file netxms.
I setup debug 4. When I connect to the server as AD user, in netxms log is
...
[12-Jun-2015 11:00:07.973] [DEBUG] LDAPConnection::initLDAP(): Connecting to LDAP server
[12-Jun-2015 11:00:07.976] [DEBUG] LDAPConnection::closeLDAPConnection(): Disconnect form ldap.
[12-Jun-2015 11:00:07.978] [DEBUG] [CLSN-0] User <user> authenticated (language=en clientInfo="nxmc/1.2.17 (Windows 7 6.1; libnxcl 1.2.17)")
...

When I couldn't connect to the server, these rows are missing and nxmc writes
Request timed out

server: CentOS 7.1, MariaDB


Thank you very much

Ladislav

#7
General Support / Active Discovery on 2.0-M4
June 12, 2015, 12:28:27 PM
Hi,

at first I installed server 2.0-M4. I setup Active Discovery for two subnets 192.168.10.0/24 and 192.168.11.0/24. The server was in subnet 192.168.10.0/24. Active Discovery found nodes in subnet 192.168.10.0/24 but no node in subnet 192.168.11.0/24. I removed this version and I installed version 1.2.7 with the same settings of Active Discovery. This version found nodes in subnets 192.168.10.0/24 and 192.168.11.0/24 without any problems
Any idea?

Thanks
Ladislav
#8
General Support / Active Discovery
June 04, 2015, 09:42:09 AM
Hi,
As I read in documentation, Active Discovery uses ICMP echo request packets and this is problem for me, because of disabled ICMP protocol on some stations.
How can I resolve this situation? Can I use a script for Active Discovery? I suppose, that it's not possible to change discovery protocol to another (for example TCP, port 3389).
I use version 1.2.7

Thanks,
Ladislav