
"All servers providing DHCP + TFTP are PXE servers and all PXE servers provide DHCP + TFTP" is a false statement. There is not a one-to-one relationship here.

Your statementĪ pxe server is actually a dhcp server + a tftp server.is incorrect. My recommendations of 3Com Boot Services and dnsmasq still apply, as I believe that both offer a ProxyDHCP service. The poster has since confirmed their scenario. On a separate box, it's most commonly listening on the DHCP port, as you mention. A ProxyDHCP service on the same box as DHCP can listen on UDP 4011. They are interested in a ProxyDHCP service, since they sayĮnabling Tftp32 dhcp is not possible.This is roughly (most commonly) what people mean by a "PXE service," when it is separate from the DHCP service. You will not find a process or a socket running for PXE.Having read the Intel PXE 2.1 specification and as a developer for gPXE and with the countless hours I've poured into supporting PXE users on its and Syslinux' mailing-lists and IRC channels, I recognize the original poster's request quite easily.

PXE is not a service but merely an environement.
