I have just started to evaluate vPro/AMT in a lab environment. I am interested in getting AMT working in and ad-hoc type small business mode (not enterprise provisioned and not using SCCM). I have installed the latest bios on my test machine (hp dc7800), installed "ME 3.2.1", and installed several other Intel components via HP.com.
At this point there is a service listening on port 16992, but when I try to connect to it using IE (example http://localhost:16992/ ) I get directed to http://localhost:16992/logon.htm , which just renders this string:
Web browser access to Intel® Active Management Technology is disabled on this computer, or the page in the address bar is unavailable.
I tried enabling basic auth on WInRM per another forum post, but not help. I also tried enabling AMT as much as possible in the "control+P" interface.
What am I missing? Thanks
Sidebar question: In the absence of something like SCCM to consume AMT info (small business scenario), what is the main interface/consumer of AMT information meant to be? Is there a management/console app from intel? Is the web interface already referred to above meant to be the main interface/experience?
I found in another post that localhost access is not suppoed to work, by design.
After opening some firewalls I tried to access this from another computer and the page fails to load. In looking at a network trace in order to try to understand the failure, it turns out that the TCP session setup to port 16992 works fine (see SYN, ACKSYN, ACK), then the calling (IE browser) machine issues a first get request and the AMT machine responds with a TCP reset, which kills the session.
So to summarize, the service is listening on 16992, inbound TCP connections are accepted, but the first get request from a caller results in a TCP reset.
As you came to the conclusion of, by design you are not able to access the AMT Web UI from the local machine. You can only access the WEB UI of the AMT client from a remote connection.
When configured for SMB / enterprise non-TLS mode, you will need to connect to the IP or FQDN/Hostname (anything that resolves to the IP Address) on TCP/IP port 16992.
In terms of your SMB console question, there are multiple ISVs that support a SMB based configuration. The selection of the ISV really depends on the requirements of your environment and costs. I would recommend consulting the http://communities.intel.com/community/vproexpert/smbtalk vPro Expert SMB Talk Zone.
Thanks for the info but I am still stuck. As I described when I try to connect to http://192.168.0.29:16992 (from another machine) no page loads. I can see that there is a service listening on this port and that I get a TCP session to the port from my web browser machine. Unfortunately no page loads.
What could be wrong with my setup? Are there any logs or config info I can gather that would help to narrow this down?
If your configuration is correct, that should work just fine. I'm assuming that you have verified that the IP address did not change on you and that you are still configured in SMB within the MEBx?
I tried re-installing/flashing 3.2.1, I tried setting everything in Control+p back up for small business mode... same behavior (LMS.exe is listening on 16992, but when trying to connect from another machine with a web browser we see a TCP session setup, follow by a GET request from the browser, followed by a TCP reset from the AMT machine no page loads ).
What could be wrong? Are there any logs/data/config that might help to narrow this down?
You may want to try and leverage the p-11480 Manageability Developer Tool Kit to connect to the client. It may provide some additional insight into root of the issue.
LOL 5 years and problem still persist... vPro (intel AMT, KVM) is also affected. Complete power cycle or connetion via Manageability Developer Tool Kit resolves this issue. When connecting to server after receiving TCP SYC, server responds sending RST.