It certainly should work :-)
Here are a couple things to try. I'm assuming that your environment is all DHCP. Once your OS boots ensure that you can remotely ping that system (windows firewall will block ping by default). Assuming you can ping the system from a remote machine try using a webbrowser to goto http://<ip address>:16992/
This should bring up the webui.
If not, you can pinging the OS by using "ping <ip address> -t" from a remote machine (you should notice a TTL of 64 or 128 depending on the OS). Go into device manager and disable the LAN device. In this case you should see a couple lost ping's followed by a ping with a TTL of 255.
If this fails then please send me the LAN driver versions and specific AMT version number. (for this test the MEI/HECI drivers do not come into play).
Here's what I tried now:
1. Browse http://ip:16992 - response in ie is 'waiting for http://ip:16992/logon.htm' which is interesting as it appears to get 'some' result back hence the 'logon.htm'. The page never loads though.
2. ping machine with ip - ttl is 126
3. I disable the NIC (Intel 82566DM-2 Gigabit) and the ttl goes up to 253
4. I browse the WebGui again and now it works (enabling the nic breaks things again)
The driver (windows 2008) is Intel's own, version 184.108.40.206 (Dell Optiplex bios version a17). I tested it on an identical machine only with an older driver, 220.127.116.11 and older bios (a09).
AMT version is 3.0.9 (for both machines).
One thing I wonder is that in the device management there is an 'other device' called 'PCI Serial Port'. The Device instance path is PCI\VEN_8086&DEV_29B7&SUBSYS_02111028&REV_02\3&172E68DD&0&1B. I wonder if that is part of the problem?
I have not tried other OS's.