Hi Mark. Sorry for the delay.

Hi Mark. Sorry for the delay. With my work on Meshcentral, I had little time to work on the MDTK. This said, these are lots of requests for MDTK updates and starting getting some test machines at my desk. So, should start focusing on it a little more in the next few weeks.

I need a little help understanding the issue. For your VPN setup, are you running a VPN client on the Intel AMT machine, connecting to a network and trying to access Intel AMT back thru the VPN? Or is the machine on a corporate network and the machine running the MDTK is running the VPN client?

If your run the VPN client & the MDTK on the same machine and connect to a network and access Intel AMT, it should work fine. In this case, the VPN will get make the MDTK machine look like it's on the corporate network and connections should route ok.

If the VPN client is on the Intel AMT machine itself, this is a bit more tricky. Your basicaly accessing the Intel AMT machine like if Command was running in the Intel AMT machine's own OS. It's like installing Commander on the local machine and connecting to 127.0.0.1. It should work, but it's not going to give you the out-of-band features that Intel AMT offers. If the OS goes down, the VPN will also drop and you will not be able to remotely access Intel AMT. Still, accessing Intel AMT using a VPN (Where the VPN client software is on Intel AMT) should work.

Let me know what type of setup you have.

Ylian