Intel AMT template connects to loopback instead of target IP
Intel AMT template connects to loopback instead of target IP
Hi,
New user of RDM here, and I was pleasantly surprised to see it has AMT support. When I try to use it however, RDM attempts to connect to 127.0.0.1:16992 instead of the target host, and crashes a few seconds later.
Connections to the target server using RDP and SSH work fine. Also other AMT clients (eg MeshCommander) connect to the target with no issues... I have configured the default redirection port on the AMT template (16992) as shown below.
Edit: Forgot to mention, I'm running RDM 2026.2.16.0 64-bit (PreJIT) on Windows 11.
4f803519-d897-4389-b5b1-0fc3ea012831.png
c0ce2a39-2c1c-405f-b39c-7fe6e88ba315.png
All Comments (1)
Hello,
Thank you for the additional information.
I was able to recreate the issue in our environment. It appears that the Intel AMT session is incorrectly attempting to connect to 127.0.0.1:16992 instead of the configured target host, which matches the behavior you described.
I've opened a bug report with our development team so they can investigate and address the issue. I'll keep your case linked to the report so we can notify you as soon as we have an update or a fix available.
Thank you for taking the time to report this and for providing the version information. Please let us know if you discover any additional details or workarounds in the meantime.
best regard.
Carl Marien