I/we(with my group) have been setting up Fixed IP(Disabled DHCP) on MEBx TCP/IP with no luck...
Can someone please help me/us whats the technique to succesfully change TCP/IP settings for FixedIP?
what are its requirements before setting up MEBx?
on our local set-up we have:
1 Lan connection (1 mac address)
126.96.36.199 BIOS version
0.0.0.0 Default gateway
0.0.0.0 DNS Server
0.0.0.0 Alternate DNS Server
on Windows network IP:
IP was not automatically obtained
subnet mask : 255.255.255.0
DNS was not automatically obtained
DNS and Alternate : 0.0.0.0
What behavior are you seeing? How is the setup failing? Are the setting getting rejected by MEBx? Are the packets not arriving at the destination? Are packets not departing from the correct ports? Please provide some details on the nature of the failure.
this message is unusual because in other machines running the same version of firmware to create provisioning.
Sorry for the failures of English that message was created from www.translate.google.com.br.
Let me ask some of the same questions roger did.
1. What version of AMT do you have? You should be able to check this in the IMSS in the OS.
2.You just want to set up AMT with a static address, correct? I believe you should just be able to set the IP address (and Mask) and the host name, and then enable either SMB mode or manual configuration. Which you use depends on the AMT version.
The AMT firmware version 188.8.131.521 is updated from the Lenovo Web site, the machine is a M57p.
Actually I'd like to do a test by connecting two machines vpro point to point and therefore need the static IP. but the error occurs in the situation of static ip.
MEBx following settings:
Provisioning SMALL BUSINESS
INTEL AMT CONFIG.
TCP / IP
NETWORK ELABLE (Y);
DHCP ENABLE (N);
IP: 192.168.0.1 (only for test);
Default gateway 0.0.0.0;
Preferred DNS 0.0.0.0;
Alternative DNS 0.0.0.0
Domain name (null);
... After confirming field it returns the error: "Intel AMT Error - Change Rejected"
and aborts the setup. I am setting up the machine out of any network that can influence the error?
It seems that he rejects any parameter that I insert, but on another machine but with amt in version (4 .(...)) the same configuration works.
Do you have any idea What can it be?
had not thought that way ... I'll do a test with a workgroup to know the result.
Please don't confuse a Windows Domain with a DNS domain. For AMT 3, you do need to set the dns domain name, but it only needs to be a placeholder, so you can use something like, amt.local. When you connect to the AMT target by IP address, it doesn't care about the domain name. The domain name only comes into effect if you turn on TLS, try to connect by machine name, or try to use any certificate based security. For just testing AMT on a deadnet, you don't need any further infrastructure, although DHCP does work much better than static IPs.
I don't mean to offend, but you didn't read my post; you MUST supply the domain name before AMT will configure through MEBx. The domain name is only a placeholder, if you don't have DNS implemented, but it does have to be set to something. Please try the experiment again, but this time, set the domain name to something like, amt.net.