I have seen that error before, but I don't know exactly what causes it. My gut instinct says that the system tried to boot from IDE-r, but the IDE-r device was not attached. If I'm right, the most likley cause is a forgotten step in commander. In commander,
1: Use the Disk Redirect menu to choose the target floppy and CDRom (you need to set both).
2: Use the Disk Redirect menu to set "Redirection Active". This steps actually attaches the IDEr device. Most consoles do this automatically, but not commander. My guess is that the error is caused my forgetting this step (which i forget all the time).
3: Use the Remote Command menu to cause the "Remote Reboot to Redirected <Floppy | CD>"
If you're following those steps and still getting the error then it's trouble shooting time. Try a different ISO. For example, Memtest++ is small, free, and known to work:http://www.memtest.org/. Try a different AMT system...maybe that is misbehaving. (BTW - if it is the system, a BIOS/firmware upgrade and/or unprovision -> provision usually will fix it). Try a different console...maybe commander is misbehaving. For any AMT 3.2 and higher system, you can try ISO Launcher:http://communities.intel.com/docs/DOC-5943. It's a great IDEr tool that makes IDEr easy. For any AMT version, RAdmin is a good alterantive for IDER (and SOL): http://communities.intel.com/docs/DOC-4309.
If none of that helps, please provide some more information so I can further assist. I need to know:
system make & model
AMT's config mode (nonTLS or sTLS or mTLS & Digest or Kerberos - if you're not sure, how did you configure it?)
Steps taken in commander
Network configuration - same subnet? network speed?
Results of troublshooting above
Anything else that you think might be helpful.
Good luck, and let me know how it goes.