According to http://community.landesk.com/support/message/12083#12083 setting the MTU in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\ doesn't do a whole lot so I haven't toyed with that.
I have however created the HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\PXE\Mtftpd\MTFTP_HIGH_PERFORMANCE key and set it both to 0 and 1 with similar results.
Tried setting the "Transmit MTFTP Large Packets" option with PXEConfig.exe as well, same result.
Oh it matters.
It is 99% of the reasons you get the PXE-E32 error.
Do you have the MTU setting or not? If not it is by default 1500. If you have it and it is less than 1500 change it back to 1500 and reboot.
You will get PXE-E32 every time no matter what if you MTU is in the 1300's which some applications actually will change you to without telling you.
I don't have the setting at all on all my interfaces.
I will try adding it anyway and see how it goes.
I have seen this be MTU about 99% of the time...about 100 cases in the past years.
A few times, a couple cases, the issue went away after updating the network card driver on the NIC.
Once and only once (so I am skeptical that the customer didn't something else too), it went away by updating the BIOS on some machines getting the issue.
If you try all those, and it is still failing, then it might be time to get a packet capture. Probably just run the packet capture on the PXE Rep, or mirror a port or something.
I've set the MTU on both interfaces on my server to 1500 and rebooted.
Tried PXE booting on a VM on the server again and was greeted by my three good friends PXE-32, PXE-32 and PXE-39.
I've setup a wireshark capture on the PXE rep while trying to PXE boot on a VM (see file attached), doesn't seem to give me much hints though.
TFTP.pcap 25.1 K
I hope you have fixed this issue by now. However, just in case someone else comes across this, I suspect the problem is that the MTFTP service has bound to the wrong IP address on the server. To fix this do the following:
Open Network Connections
From the Menu bar (File, Edit...) select Advanced, then Advanced Settings
On the adapters and bindings tab, make sure the connection (NIC with the right IP) is at the top of the list
Restart the LANDesk PXE service and the MTFTP service
That should do it. LANDesk PXE isn't supported on a machine with two NICs, but this normally resolves the issue you are seeing
Had a similar issue. Spent a lot of time trying all sort of solutions mentioned here and in other articles with no luck. After a while I discovered that someone had installed Cisco VPN client on the PXE rep. Uninstalled the Cisco client and problem went away. PXE boot without errors.
Tks Tanner, modifing the order in the "Adapters and Bindings" solved my issue with the PXE boot, when the wrong NIC (the latest NIC configured in the server) was in the top of the list the PXE try to TFTP to the wrong IP (IP used in my iSCSI Connection), when I put the correct NIC in the first place and restart the PXE Service the TFTP started to work.