MeshCommander is a Intel(R) Active Management Technology (Intel(R) AMT) remote management tool. It's feature rich and includes a built-in remote desktop viewer for Hardware-KVM, a Serial-over-LAN terminal, IDER-Redirection support and much more. MeshCommander is built on web technologies and runs on many plaforms. In addition to being available as a stand-alone tool, MeshCommander was built to be very space efficient to that it can be uploaded into Intel AMT flash space to have it served diretly from the Intel AMT web serve.
MeshCommander can detect the device via scan, but when I try to connect, the connection times out.
I note in your MeshCommander tutorial video, that when configuring TLS, the AMT device starts out in non-TLS mode before configuring the certificate and enabling TLS.
In trying to troubleshoot this system, I downloaded some Intel tool onto the PC that said that AMT was already in TLS-mode (as shipped). I'm not sure if this might be the reason that MeshCommander is unable to connect.
Hello,
This is a question, rather than an issue.
I have configured MEBx via manual setup and enabled AMT on a Dell Precision 3660.
So, I know the user and the password.
I can connect to the WebUI via https://ip_address:16993
MeshCommander can detect the device via scan, but when I try to connect, the connection times out.
I note in your MeshCommander tutorial video, that when configuring TLS, the AMT device starts out in non-TLS mode before configuring the certificate and enabling TLS.
In trying to troubleshoot this system, I downloaded some Intel tool onto the PC that said that AMT was already in TLS-mode (as shipped). I'm not sure if this might be the reason that MeshCommander is unable to connect.
Basically I'm after troubleshooting suggestions.