topic Ylian, in Intel® Business Client Software Development

MeshCommander 0.6.8 Uncaught TypeError : Cannot read property 'getPeerCertificate' of null

CBial — Tue, 21 Aug 2018 12:39:31 GMT

Hello!

My usage scenario is as follows: I have vPro machine NUC7i5DNH on the internal network. Via router port forwarding the 16993 port is exposed on the internet (IPv4). Now, connecting to the external ip:16993 with MeshCommander v 0.6.8.

All seems to work except for Remote Desktop and SOL. First click to open Remote Desktop Connection gives the following in debug (yes, i am running MeshCommander.exe -debug)

commander.htm:18 - Uncaught TypeError: Cannot read property 'getPeerCertificate' of null
commander.htm:18 - g.getPeerCertificateFingerprint
commander.htm:1251 - connectDesktop
commander.htm:1 - onclick

The result is that connection is not possible.

Can you re-create the issue? Can this be fixed in MeshCommander?

Hey Chris

Joseph_O_Intel1 — Tue, 21 Aug 2018 14:56:06 GMT

Hey Chris

The ports 166992 (non TLLS) and 16994 (TLS) are used for authentication and AMT management,

However when we talk about AMT KVM (remote Desktop), and Redirection (IDE-R, USB-R, SOL) we move to 16994 (non TLS) and 16995 (TLS).

From the description you are using, you will need to forward 16993 and 16995

Joe.

Joseph,

CBial — Tue, 21 Aug 2018 18:43:02 GMT

Joseph,

Thanks for that. So simple... I was simply misled by the fact that if MeshCommander is being run in firmware mode it is using only single port...

Sorry for trouble.

Chris

Hi Chris. Your are right that

Ylian_S_Intel — Tue, 21 Aug 2018 22:32:50 GMT

Hi Chris. Your are right that when loaded in firmware, MeshCommander will do SOL/KVM using a web socket on port 16992/3. However, you got my attention... the problem reported above with "-debug" is not related to the firmware version of MeshCommander. I am curious, can you give me context as to what you are doing?

If you got the standalone MeshCommander to show these errors in the debug console, I have things I need to fix! I would really like to replicate this.

Thanks in advance,
Ylian

Ylian,

CBial — Wed, 22 Aug 2018 05:32:00 GMT

Ylian,

What I did was as follows:

1. I had NUC7i5DNH with certificate loaded facilitating TLS connection. NUC stayed on internal private network

2. I had forwarding enabled ONLY for port 16993 to allow connection from internet.

3. Connected with MeshCommander outside of internal network to my router, port 16993. Connection was succesfull and certificate accepted.

4. Clicked connect on remote desktop part of Mesh Commander - this is the moment where the exception appears. And it appears only on first click on connect after Mesh Commander is started. Even disconnecting Mesh Commander from AMT and reconnecting again and clicking on KVM connect again does not re-generate the exception.

This is the whole scenario...

Kind regards,

Chris.