I was wondering if you enabled AMT on your Dell system? When you refer to your static IP address, is that for your host OS? You will need to go into the BIOs, configure the ME (tell it to use Intel AMT) and then you will have to configure AMT and give it a static IP address as well. This is the IP address that you would connect to via the Web UI. (If you are using Static IP, your AMT Client will have a different IP address than your Host OS.)
You will have to change the ME password (to a strong password)if this is the first time you have gone into it.
Once AMT is enabled, make sure you can ping the system (using the AMT IP address.) If you have a firewall enabled you also won't be able to connect.
Check out the Start Here guide for some help.
Also check out this blog on setting up an AMT Client.
I hope this helps.
You are not supposed to connect to the AMT system locally through WebUI or ping locally even if you have static IP. Another question is do you have LMS and HECI drivers installed on your system?
I wonder if your trouble is not a network topology issue ... did you configure your AMT host and AMT device with static IP on the same subnet? in that case the switch or hub will not forward any packet back to the same port and a transmitted packet from the host will never get back to the AMT device (there is no loopback).
However if you are using different subnet with correct default gateway than can route packet from one subnet to the other you will be able to ping your AMT device from the AMT host...
did you try this?
Well, some more info (thanks for keeping along with me...)
I ran Outpost under a debugger and I see that it fails connecting while invoking a web service (probably the first one) with a method name "GetCoreVersion".The exception message is:
The underlying connection was closed: An unexpected error occurred on a receive.
So still it seemslike a networking issue.
In the static IP mode with two IP addresses for the AMT device and host system, you won't be able to ping each other even ifthey are on different subnet. I have forwarded your Outpost question to Ylian.
Hi there. I just released Intel AMT DTK v0.51x a few minutes ago. You coudl try that first.First aword on AMT/LMS/Outpost:
The way AMT is hooked up to the Gigabit network adapter makes it impossible to access using the OS loopback adapter (127.0.0.1) any traffic you send to 127.0.0.1 will never reach the network hardware and so, never reach AMT.
So, there is a way to talk to AMT using a HECI driver, it's a local driver that talks directly to AMT using a customer driver. A service called LMS ("Local Management Service" I think) will listen to TCP ports 16992 and 16993 and forward the traffic thru the HECI driver to AMT.
As you can see, when you contact port 16992 on the local computer, the traffic is just captured byLMS and forwarded to AMT using a driver. It's not going thru the network at all. Also, network configuration on AMT will not affect the HECI driver or LMS.
Here is my checklist of things that be cause Outpost to not be able to connect:
Hope this helps,
Ylian (Intel AMT Blog)
I am stumpted. First, when LMS is working and you use a web browser to access 16992 on LMS, youmay not see the Intel AMT web page, it depending on the AMT version.
If you use Intel AMT Reflector, you need to run reflector on a different computer that does not have Intel AMT. In that case, you can reflect back 16992 to 16995 connections back to your own computer and it will be just like you are accessing AMT from a different computer.
Other than that, I am stumped, it should work... try updating your firmware.
Ylian (Intel AMT Blog)
Hi - one more thing... Could you verify if you have enabled SOL and IDER in your AMT Configuration? The AMT configuration does not enable Serial over Lan by default and this is what AMT Commander uses.
To enable this:
Hit CTRL-P during boot up to enter the AMT configuration Tool
Select Intel AMT Configuration
Press Y acknowledging changes
User Name and Password should be enabled
Serial over LAN should be enabled
IDE Redirection should be enabled
One more question - could you check your AMT configuration and make sure you entered the Host Name for the AMT client and that it is the same as the Host Name for the OS - if you haven't done that, you will be able to ping, but it will be the host OS that is answering, not the AMT Client.
You will not be able to ping the AMT Client from the Local AMT System. Ever. (I'm still not clear on if this is what you are trying to do...) The LMS and HECI software are used for APIs that are designed to work on the Local AMT Client. There are many operations that won't work locally and pinging is one of them.
This page has a link at the bottom to a video tutorial on Outpost (Intel AMT Outpost agent (v0.11)) Please go through it and see if this is what you are trying to do here.