Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've a PXE server for network installation. Everything was working fine until we virtualized the server using VMware ESXi 5.1.

When we try to boot a machine through the network, it got an IP from the DHCP server (running on the same machine) and it waits for TFTP until we get a timeout.

We are running Debian 7 Wheezy, with isc-dhcp-server and tftpd-hpa. Here are my conf files:


allow booting;
allow bootp;`

default-lease-time      1800;
max-lease-time          3600;

option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option PXE.discovery-control code 6 = unsigned integer 8;
option PXE.discovery-mcast-addr code 7 = ip-address;

class "PXE" {
    match if substring(option vendor-class-identifier, 0, 9) = "PXEClient";
    filename "pxelinux.0";
    option vendor-class-identifier "PXEClient";
    vendor-option-space PXE;
    option PXE.mtftp-ip;



And I can confirm that tftpd is running and listening on the server:

netstat -a | grep tftp
udp        0      0 *:tftp                  *:* 

Thanks in advance,

share|improve this question
Can you download pxelinux.0 using a TFTP client? What's that next-server setting pointing to? What method did you use to virtualize the system? – Shane Madden Jun 9 '13 at 1:26

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.