Mesh Commander remote desktop unable to connect NUC12WSKv5 ME v16.1.2

[bleomycin]

Mesh Commander is unable to connect to the remote desktop of my NUC12WSKv5 with ME v16.1.25. The error thrown is "KVM disconnection, this may indicate that Intel AMT is unable to capture the display (Try RLE8 encoding), or unsupported GPU."

I've tested every Image Encoding setting one by one with the same result. I've launched with nw.exe -debug -norefresh and nothing shows in the debug window. Most other functions of Mesh Commander seem to be functioning fine, just not remote desktop.

debug log file attached.

Thanks for any help!
log.txt

[jsastriawan]

Not sure if this will help.

1. Can you check if the KVM features is enabled? Probably System status panel.
2. Check if HDMI ports are connected to display. AMT KVM requires display to be connected.
3. Have you tried upgrading the NUC to the latest BIOS? There may be some issue with your current BIOS.

[bleomycin]

Not sure if this will help.

1. Can you check if the KVM features is enabled? Probably System status panel.
2. Check if HDMI ports are connected to display. AMT KVM requires display to be connected.
3. Have you tried upgrading the NUC to the latest BIOS? There may be some issue with your current BIOS.

Thanks for the tips. Unfortunately i’ve already done all of those things. I even considered trying to downgrade the bios but haven’t been able to find older ones yet.

[bleomycin]

I apologize for wasting your time. This is my first time using any type of AMT vPro device. For whatever reason the remote desktop connection absolutely refused to connect to this device until windows was installed AND the intel gpu drivers/ME drivers were also installed. I was attempting to connect to the bios and to windows but without these drivers installed yet as I intend to run linux on this device ultimately anyways. I have 0 idea why this is the case for an out of band management device but now everything is functioning properly including access to the BIOS.

[jsastriawan]

You are not wasting time. This is definitely an interesting case. I will try to ask to check internally. Did you connect your screen to a 4K monitor? The process of pulling high resolution display framebuffer, compress and send over network may be too much if the scaling is not set in the firmware.

One thing that I looked at the log file you sent, AMT is sending RFB 4.0 protocol negotiation whereas MeshCommander only supports RFB 3.8.

[bleomycin]

Thanks! I'm using a 1440p monitor, initially at 60hz but now at 144hz. So far everything is still working well after installing all of the intel drivers, whatever that did to kick start things.

I've power cycled a bunch of times, disconnected the display and reattached, booted to linux and it all continues to work great including access to the bios.

[clumbo]

I have the exact same NUC, you need to change in the bios to virtual display emulation if running without monitor, I had to tweak a few bios settings but that was the main one