zlacker

[parent] [thread] 3 comments
1. Haemm0+(OP)[view] [source] 2020-07-23 15:49:03
It works, however you need a non-free special client called VNC Viewer Plus [1]. Afaik it is Windows only. You can enable regular VNC protocol capabilities for AMT[2], but then you can't use the interesting stuff anymore.

[1] https://www.realvnc.com/en/products/viewerplus/ [2] https://blog.michael.kuron-germany.de/2011/10/using-intel-am...

//edit: link [2] added.

replies(2): >>tyingq+F2 >>vetina+bE
2. tyingq+F2[view] [source] 2020-07-23 16:01:26
>>Haemm0+(OP)
This seems to show a reasonable option from Linux: https://www.cyberciti.biz/faq/remotely-access-intel-amt-kvm-...
replies(1): >>plett+sd9
3. vetina+bE[view] [source] 2020-07-23 19:11:30
>>Haemm0+(OP)
You can use meshcommander[1], which has a nodejs version that runs under linux and mac.

Then you just have to pay attention to your certs (if you are using https), because browser policy will apply.

[1] https://www.meshcommander.com/meshcommander

◧◩
4. plett+sd9[view] [source] [discussion] 2020-07-27 11:24:42
>>tyingq+F2
I've used instructions similar to those to get AMT KVM working with a normal VNC client, it works fine. The only catch is that the AMT seems to intercept all traffic to port 5900 coming in through the NIC, not just that addressed to the IP of the AMT. It's only the "legacy" port 5900 VNC which is affected, the other ports such as 16992 for AMT's web admin are unaffected.
[go to top]