search

Ylianst / MeshCentral

A complete web-based remote monitoring and management web site. Once setup you can install agents and perform remote desktop session to devices on the local network or over the Internet.
https://meshcentral.com
Apache License 2.0
3.88k stars 528 forks source link

CIRA setup script - error from client on connect #103

Open djsakisd opened 5 years ago

djsakisd commented 5 years ago

Hi @Ylianst

I tried to add an intel AMT client with cira setup script, but client can't connect to server. Server FQDN is valid and if i start meshcentral server with --mpsdebug i can see these logs while client tries to connect.

MPS <-- (93):c000000001000000000000000380b362d130c3e31182a540a8f0a2a53600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 MPS <-- (23):05000000126175746840616d742e696e74656c2e636f6d MPS --> (23):06000000126175746840616d742e696e74656c2e636f6d MPS <-- (68):3200000010346270694a6a673131347a53776d7561000000127066776440616d742e696e74656c2e636f6d0000000870617373776f726400000000084140786577397274 CIRA connection for unknown node. meshid: mesh//4bpiXXXXXXXXXXXXXXXX@qnUyXXXXXXXXXX, uuid: undefined XXXXXXXXXX is hiden values for security Do u have any idea why is this happening , is this a bug ? Intel AMT agent version 9.1.42.3002

Ylianst commented 5 years ago

This is an interesting report, I see you found the --mpsebug option. The server uses the Intel AMT platform GUID as a unique computer identifier for pretty much everything. The fact that uuid is undefined is of interest. I need to check this out further...

djsakisd commented 5 years ago

Thanks @Ylianst for checking this , if you need any further info i'd be glad to provide with. In the meantime i'll try to find an earlier firmware for AMT to test this.

The pc that gives this error is an Hp eliteDesk 800 G1

Ylianst commented 5 years ago

Do other PC's generally work and it's only a problem with that one? Also, are you using a device group with agent? or Intel AMT only? - Thanks.

jsastriawan commented 5 years ago

Another check, can you also look at system UUID by running MeshCommander or MeshCmd AMUUID? I have seen many times that UUID is no longer unique. Not sure how it becomes null/undefined.

djsakisd commented 5 years ago

Hi @Ylianst and @jsastriawan

Thank you all for the quick responses

I verified that this problem only happens when group is mesh agent type, with intel AMT groups CIRA setup script works fine.

Should i close the issue ?

Ylianst commented 5 years ago

Hi. No, leave this issue open. It's still a bug I need to get fixed. Not sure when I will get around to it, but I do want it tracked.

luckybruce commented 5 years ago

hi @Ylianst we encountered the same issue here, when the device group is set to use AMT only, the script will work fine, if the device group is set up to use software agent, then --mpsdebug will throw CIRA connection for unknown node error.

luckybruce commented 5 years ago

hi @Ylianst, i am happy to report that this issue seems to be fixed since updated to 0.3.7-a

Ylianst commented 5 years ago

Nice. I was not even thinking of this specific issue and I did fix a few things with how CIRA nodes are found in the database. Let's keep this issue open for just a while longer to make sure everyone is ok and it's really fixed.

dinger1986 commented 9 months ago

last comment makes me think its been fixed @si458