Hmmm, I don't think so, but I'll give it a try. The machine I'm tryng to image is one that I've imaged many of previously, and I get the same error on an older machine type that I've been trying to troubleshoot HII troubles with, but then suddenly last Thursday, after we fixed the DHCP errors, I started getting that MTFTP server not having an IP error.
I'll try restarting the service and possibly changing tha registry value on the PXE Rep, as I don't think it's the BIOS problem.
Well if you've imaged that specific hardware before, then that's likely not your problem. Note that you don't want to do those registry changes (ie turning off mtftp) unless you have to. It will only slow down your image deployments.
Have you tried simply restarting your PXE rep?
Tried a restart, and also tried redeploying the rep... Still getting the no IP error.
It would be interesting for you to capture a Wireshark of the PXE process.
The following article illustrates it.
The client should ask for an IP address and for a boot server. It may be that the boot server information being handed back by DHCP is incorrect.
Check that the DHCP options do not include boot server information.
Also ensure that the PXE MTFTP service is running on your PXE representatives. Restart both PXE services for good measure.
Can you see the device pull an IP from DHCP? If so I would check out the registry key on the PXE server has the correct IPs: HKLM\Software\Wow6432Node\Intel\PXE
If so you can turn logging on to verify PXE is doing its job:
I know when upgrading I had to push the PXE Rep Uninstall, reboot, and then push the PXE Rep Install from LDMS.
Thanks for the help and suggestions everyone, we got it figured out. The port my imaging switch was plugged into was configured for the wrong VLAN and so it was not pulling an IP. Just threw me off that it went from a DHCP error to that strange IP error.