PXE-E51: No DHCP or proxyDHCP offers were received.

  • Hello, When I try to take an image of a machine, I keep getting this message.

    PXE-E51: No DHCP or proxyDHCP offers were received.

    NOt sure what I am doing wrong

    I have an inhouse DNS and DHCP server already setup.

    Please help

    here is my /etc/dnsmasq.d/ltps.conf file.

    # Sample configuration for dnsmasq to function as a proxyDHCP server,
    # enabling LTSP clients to boot when an external, unmodifiable DHCP
    # server is present.
    # The main dnsmasq configuration is in /etc/dnsmasq.conf;
    # the contents of this script are added to the main configuration.
    # You may modify the file to suit your needs.
    # Don't function as a DNS server:
    # Log lots of extra information about DHCP transactions.
    # Dnsmasq can also function as a TFTP server. You may uninstall
    # tftpd-hpa if you like, and uncomment the next line:
    # enable-tftp
    # Set the root directory for files available via FTP.
    # The boot filename.
    # rootpath option, for NFS
    # kill multicast
    # Disable re-use of the DHCP servername and filename fields as extra
    # option space. That's to avoid confusing some old or broken DHCP clients.
    # PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
    pxe-prompt="Press F8 for boot menu", 0
    # The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
    # Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
    # This option is first and will be the default if there is no input from the user.
    pxe-service=X86PC, "Boot from network", undionly.kpxe
    # A boot service type of 0 is special, and will abort the
    # net boot procedure and continue booting from local media.
    pxe-service=X86PC, "Boot from local hard disk", 0
    # If an integer boot service type, rather than a basename is given, then the
    # PXE client will search for a suitable boot service for that type on the
    # network. This search may be done by multicast or broadcast, or direct to a
    # server if its IP address is provided.
    # pxe-service=x86PC, "Install windows from RIS server", 1
    # This range(s) is for the public interface, where dnsmasq functions
    # as a proxy DHCP server providing boot information but no IP leases.
    # Any ip in the subnet will do, so you may just put your server NIC ip here.
    # Since dnsmasq is not providing true DHCP services, you do not want it
    # handing out IP addresses.  Just put your servers IP address for the interface
    # that is connected to the network on which the FOG clients exist.
    # If this setting is incorrect, the dnsmasq may not start, rendering
    # your proxyDHCP ineffective.
    # This range(s) is for the private network on 2-NIC servers,
    # where dnsmasq functions as a normal DHCP server, providing IP leases.
    # dhcp-range=,,8h
    # For static client IPs, and only for the private subnets,
    # you may put entries like this:
    # dhcp-host=00:20:e0:3b:13:af,,client111,infinite

    Tom Elliott – Edited to wrap the code in triple backticks so we can actually read the config more properly.

  • This post is deleted!

  • @cnkpadobi If this thread’s original problem is solved, please create a new thread.

  • Moderator

    @cnkpadobi Lets make sure we have the same terminology. FOG is capable of deploying an image to a target computer, but the target computer does not boot correctly once deployed?

  • Can’t seem to get my machines to deploy image just keep rebooting… Not sure what i am doing wrong![5_1479343453124_161116_042208_25.jpeg](Uploading 100%) ![4_1479343453124_161116_042208_24.jpeg](Uploading 100%) ![3_1479343453123_161116_042208_23.png](Uploading 100%) ![2_1479343453122_161116_042208_22.jpeg](Uploading 100%) ![1_1479343453121_161116_042208_21.jpeg](Uploading 100%) ![0_1479343453120_161116_042207_20.png](Uploading 100%)

  • I have another question, I have one machine is that is on a continuous loop.

    Check Task Management in the web interface to see if there is a task for this device. Tasks don’t just go away. They will stay in task management until either they are canceled or completed.

    Lastly is there a way to set the fog registration screen with the options to stay a bit longer?

    Web Interface -> FOG Configuration -> iPXE Boot Menu -> Menu Timeout (in seconds):*

    Also, any additional questions, please ask them in a new thread.

  • Thanks for the help…

    I have another question, I have one machine is that is on a continuous loop.
    Seen pic for the last screen before it loop. This was a machine that I tested and took ![0_1479240011624_20161115_115236.jpg](Uploading 100%) image on before.

    And will not get to the quick registration screen. Lastly is there a way to set the fog registration screen with the options to stay a bit longer?


  • Moderator

    @cnkpadobi said in PXE-E51: No DHCP or proxyDHCP offers were received.:

    So DHCP is done is on each subnet.

    Does each subnet have its own dhcp server or do you have a central dhcp server? I can say that deploying images across an MPLS circuit will be very slow.

  • So DHCP is done is on each subnet.

    The Main one we been working on is 192.168.0.x
    One of the sub sites 10.10.1.x

    However the subnet and the main site is connect by MPLS Network

  • Moderator

    @cnkpadobi well that opens up a bunch more questions about your setup. The main one is, do you have a dhcp server at each site?

    But to get this working, let’s focus at just one site and one subnet. When you introduce a router between the client computer and the dhcp server you’ll need to use a dhcp helper service. When the fog server is on a different subnet from the pxe booting computer the dnsmasq service will not hear the dhcp hello broadcast.

  • no not all we have 15 different location as well.

    How do I setup for my network to received computers from the different subnet.

  • Moderator

    @cnkpadobi said in PXE-E51: No DHCP or proxyDHCP offers were received.:

    question was looking at the wireshark file. Since it has so many ip address in it… was thinking it may be picking up my voip phones as well… Is that possible?

    The pcap file is fine. It looks like you have a busy networks. We specifically created the tcpdump line to only include dhcp, dpchproxy and tftp traffic. This all looks normal, the dhcp inform lines are just the devices (mainly windows) telling the dhcp server, hello I’m still here.

    Voip phones do add a bit of information since voip phones some times uses the next server (dhcp option 66) to locate the pbx server. By enabing dnsmasq and pointing it to the fog server you “may” run into provisioning issues with your voip handsets. But if your dhcp server didn’t ahve option 66 set when you started your voip phones may not use auto provisioning. Even if we did run into a conflict with dnsmasq we can make them happy together.

    Are all of your computers on the same subnet or do you have a network router in your environment? (i.e. you have multiple sites, or buildings on your campus where you have a router to segregate traffic?)

  • @cnkpadobi It depends on how your network is laid out. Typically VOIP is put on a different network and also a different vlan which makes it impossible to see unless you’re connected to the same vlan. The addresses you see are likely broadcasts from other systems. ARP requests, DHCP Discovery and Requests, WhoIs requests, ICMP traffic, and other things. This stuff is normal network chatter.

    If you want to filter what you’re seeing, in the filter box in wireshark, put in bootp and you’ll only see DHCP related traffic.

  • question was looking at the wireshark file. Since it has so many ip address in it… was thinking it may be picking up my voip phones as well… Is that possible?

  • ok got it to pxe boot… seems to work somewhat.

    Was able to take image but still having issues deploying0_1478830627175_output.pcap

  • Moderator

    @cnkpadobi Not sure, but the pcap was damaged some how after booted. When you pxe boot the one that fails, please pay attention to the IP address being issued. You should see that on the bios screen just before it transitions over to iPXE. So you have to read fast. That will tell me that I’m looking at the right system.

    One question, the system that doesn’t boot is that a uefi system or bios (legacy mode) too?

  • hmmm… ok why would the other machines not boot? will try to get another log file

  • Moderator

    @cnkpadobi I see a normal pxe booting process for, That looks beautiful. I see both your dhcp server and the dnsmasq respond and then the client asks for the undionly.kpxe from the tftp server.

    Looking through the rest of the file.

    The rest of the file seems to be damaged. But I can see that iPXE booted well.

  • Ok follow the steps.

    1. Turn off the watchguard DHCP options.
    2. enable dnsmasq on server
    3. Got the first machine to pxe boot and was able to take snapshot of the machine.

    While taking a snapshot of the machine, I decided to see if I can pxe boot and register another machine.

    HOwever, I got the origal mesage again… HOwever the other machine is still working.

    Here is a capture of my log files 0_1478826719275_output.pcap

  • Excellent work Sebastian and George. This makes sense.