Connection issue with AMT

[Deximy]

I have a LENOVO P700 workstation with AMT enabled. Now I can access http://192.168.0.4(LENOVO's IP):16992 without any issue:

However, when I try to access this endpoint from other computers in the same subnet, I always get error "connection refused":

Some of clues that may help to narrow down the issue:

+ I configured AMT in SMB mode.

+ I enabled DHCP and set a static IP for workstation on router. I also tried to configure it manually, but no luck as well.

+ No matter whether I set host name or not, the issue always happens.

+ I have tried to reset AMT completely. It didn't help too.

Any suggestions will be appreciated.

[Arun_Intel1]

Hi Deximy,

Greetings!

We see that the issue where you can access the Intel AMT WebUI (http://192.168.0.4:16992) locally on your Lenovo P700 but get "connection refused" from other computers on the same subnet is commonly caused by AMT network configuration, firmware, or firewall/network isolation. Below are the most probable causes and specific troubleshooting steps:

Check points to be considered that can help to isolate the issue:

Firewall Blocking External Connections:

The most common reason is that the host OS (Windows or Linux) has firewall rules blocking incoming connections on port 16992 from external IPs. When accessing locally, the firewall rules often allow localhost connections but block LAN connections.

AMT Not Listening on the LAN:

Make sure AMT is actually bound to the network interface used by your LAN. AMT is hardware-based and should listen for external traffic by default, but certain firmware or BIOS bugs can restrict access to only localhost, especially in SMB mode or after misconfigurations/reset.

Incorrect DHCP / Network Setup:

SMB (Small Business Mode) AMT uses the system's shared NIC IP address. Ensure:

BIOS/ME configuration reflects the current static IP or DHCP reservation.

The IP address shown in the AMT configuration page matches what's set on your router or by DHCP.

AMT “External” Access Disabled:

Some AMT configurations or firmware revisions allow local-only WebUI access as a security precaution (for example, after certain resets or incomplete setups). Confirm remote (“External”) access is enabled in the AMT settings via MEBx (Management Engine BIOS Extension).'

Check network configuration: verify that AMT is set to respond to traffic from your LAN, not just “localhost” or “loopback.”

Firmware/Bios Reset and Updates

Updating the BIOS and ME firmware can resolve known AMT bugs—especially for older platforms like the P700. After updating, reconfigure AMT from scratch.

Network Segmentation/Router Settings

If your router has guest isolation, VLANs, or other client isolation features enabled, devices may not be able to connect to each other even on the “same subnet.” Verify isolation is OFF.

If the above steps fail:

Check that your browser isn't caching a failed login or blocked port and try with a different browser and share your observation.

In summary, the most likely reason is the firewall on the host or an AMT/firmware setting that restricts access to localhost. Disabling the host firewall, verifying AMT network binding in MEBx, and checking for network isolation should resolve the issue in most cases.

Thanks & Regards

Arun

Intel Customer Support Technician

[Deximy]

Thank you for your reply. I will have a try.

[arss5]

I'm having the same problem, did all the mentioned steps and still isn't working. Can you update if there is any progress?

[Arun_Intel1]

Hi arss5,

Please try with https://FQDN:16993 instead of 16992 and share your observation with the screen shots, if you are able to access the AMT Web UI.

Thanks & Regards

Arun

Intel Customer Support Technician

[Arun_Intel1]

Hi Deximy,

Thank you for contacting Intel, please feel free to revert for any further query!

Thanks & Regards

Arun

Intel Customer Support Technician

[Deximy]

Hello @Arun_Intel1 ,

Thank you for your follow up.

Unfortunately, FQDN doesn't work and I get the same error code as well.

To better investigate this issue, I have already used Wireshark and confirmed the issue has nothing to do with Windows firewall, as there is no packet received at Windows level from my workstation, while my laptop received TCP_RST packet again.

Any further explanation or suggestions will be appreciated. Looking forward to your reply.

Best regards

[Arun_Intel1]

Hi Deximy,

To further assist, please share the ECT log of the endpoint, whose AMT web UI you are trying to access.

Steps to collect the Intel® EMA Configuration Tool (ECT) Logs from the endpoint:

1. Download the tool from the following link: Intel® EMA Configuration Tool
2. Installation:

• Download and unzip the tool.
• Double-click the .msi file and follow the installation prompts.

1. Run the Tool:
2. a. Open a command prompt as an administrator (or use Windows PowerShell*).
3. b. Navigate to the installation folder (default: C:\Program Files (x86)\Intel\EMAConfigTool).
4. c. Run the following command:
5. EMAConfigTool.exe --verbose

Thanks & Regards

Arun

Intel Customer Support Technician

[Arun_Intel1]

Hi Deximy,

Gentle reminder to check if you had an opportunity to collect the ECT log from the endpoint under consideration.

Thanks & Regards

Arun

Intel Customer Support Technician

[Arun_Intel1]

Hi Deximy,

Please feel free to revert for any further query!

Thanks & Regards

Arun

Intel Customer Support Technician

[Arun_Intel1]

Hi Deximy,

Please note that by default, the remote access to the machine is disabled on the endpoints. We need to enable the option called Activate Network Access in MEBx.

Please find the screenshot in the attachment to activate network access in MEBx.

You may use http://ip_address:16992 or https://ip_address:16993

Kindly share your observation once you perform the plan of action given above.

Thanks & Regards

Arun

Intel Customer Support Technician

[Arun_Intel1]

Hi Deximy,

Thank you for contacting Intel!

Please feel free to revert for any further query.

Thanks & Regards

Arun

Intel Customer Support Technician

intel.com/vPro